[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.