[quesera]

As a counterpoint of sorts, if you are accustomed to vim, moving to neovim entails almost zero switching friction.

Everything works just like it's supposed to. In fact sometimes I get neovim instead of vim (when I run "vi" from the shell) and I don't even notice.

I have a fairly simple vim config.

I'm sure this means that I'm missing out on all the great new things about neovim, and maybe I'll get there some day. But I am happy with how vi/vim/neovim work reliably and consistently every time.

[plugin-baby]

> moving to neovim entails almost zero switching friction

As a counter-counterpoint: I tried switching to neovim a couple of weeks ago, and gave up after half a day trying to get syntax highlighting working.

[worksonmine]

Strange considering neovim has syntax=on by default and it's not even needed in the config. What distro are you using?

[quesera]

I love that the usernames of the two parent comments are so fitting:

  plugin-baby: (complicated setup?) I see errors

  worksonmine: WFM

No disparagement intended. I'm sure you're both right.

My vim config is simple, and neovim handles it well. Including syntax highlighting (some custom). I don't like some of the defaults as much as what shipped with vim, but I know I could configure them out if I cared enough.

[plugin-baby]

quesera: also fitting, as you’re happy to go with the flow :-)

Why do you use neovim when it sounds like you’re marginally less happy with it?

[quesera]

Ha, well, consistent with the thread here:

I don't use neovim, per se.

But sometimes when I run "vi" on one of the various systems I frequent, neovim is what I get.

It doesn't break any of the config I've set explicitly, and doesn't give me wildly unexpected settings aside from that, so I'm good. :)

[plugin-baby]

Sorry, should have been more specific. I was trying to get tree-sitter working, as that seems to be the big differentiator for vim vs. nvim.

[vander_elst]

> Everything works just like it's supposed to

There are different defaults for the pane management and the terminal. The vim defaults, IMO, allow a more consistent user experience. E.g. when you are in a vim terminal and you go to normal mode to yank some stuff to put it in the other pane with the code, nvim defaults adds line numbers to the terminal that need to be cleaned up afterwards, vim just does not add them. This is just one small example, but there are several edge cases where the vim defaults behave like I would expect and nvim either does something unexpected or it lags or it crashes.

[gpanders]

>E.g. when you are in a vim terminal and you go to normal mode to yank some stuff to put it in the other pane with the code, nvim defaults adds line numbers to the terminal that need to be cleaned up afterwards

Maybe I'm misunderstanding, but the Nvim terminal does not do this, at least by default (maybe some plugin enables this "feature"). If you yank some text from a terminal buffer in Nvim and paste it into another buffer with p, no line numbers are added.