I mean, most of those things can be done in regular vim too. I’m probably going to switch eventually, but I haven’t really had any issues with vim that would motivate me to switch, and I haven’t really encountered anything super useful that nvim has that vim can’t also do. Though, I’ll admit lua is tempting, and better defaults are certainly a plus!
For search highlighting, the relevant options are :set hlsearch and :set incsearch. nvim just has those enabled by default. nvim also has a binding Ctrl+L to clear the search highlight. This isn’t in vim by default, but the vim-sensible plugin also adds it.
What do you mean by cw putting a dollar sign? I don’t think I’ve ever encountered that.
Edit: the vim syntax for Ctrl+L got eaten by markdown.
Is the LSP support in nvim better than what you can get with plugins? I’m using coc.nvim with vim and yeah it is really cool.
I didn’t know about that
:termdifference. I think I prefer vim’s behavior there.If you have
:set hidden, then the current buffer will be hidden when you open a different file, and you won’t be prompted. Without it, vim doesn’t allow hidden buffers and will discard the buffer when you open a different file (which is why it prompts you). Vim’s defaults are very odd sometimes.Huh, that
cwbehavior in vi does seem pretty jarring. Interesting, though. It makes sense why it was like that.