might switch from alacritty to kitty almost just for this (although I’ve been meaning to for a while). the “immediately get scroll back into an nvim buffer to edit as a command” is pretty sweet
another way to start is to only do small configurations at first. as you code maybe you realize you want a tool that shows git diffs, install a plug-in that does that. over time, you gradually build your config. maybe you want to start using leader
for custom key maps. a couple days later maybe you think you want a file picker so you add telescope. this 100% will take longer, but you’ll intimately understand why every line in your config is there.
without more information, the most straightforward way is to disable your plugins one at a time and test if things are working (could go the other direction: start from no plugins, and install them one at a time). do this by commenting/uncommenting lines in your config and rerunning sync/clean/install or whatever with your plugin manager.
ideally youd have some idea about what specifically is breaking for you. since you say completion maybe start with whatever you use for that (cmp, mason setup, coc, deoplete, ycm)?
edit: forgot to say, but if you post your config that could be helpful in case there’s an obvious err somewhere. is it all macros that fail or only some with specific motions?
this was the first lua plugin I migrated to back when lua support was merged! efficiency difference was noticable, great plugin.
sadly no; position of hint is determined by the LSP server.
you could use this plugin (now archived) which was the way many people used hints pre-0.10:
https://github.com/lvimuser/lsp-inlayhints.nvim