@digital_carver @vim
I thought about trying neovim because apparently you can replace GUI text boxes (like in your browser) with a neovim instance. I’m not compelled to try it out soon though. Vim’s ubiquity is a great reason for me to stay.
@digital_carver @vim I didn't find that hard. I had a lot of cruft on my vimrc and that was a good opportunity for some cleaning up.
So far, not seeing that big change, but I'm hopping NeoVim 0.5 is released soon, so I can use something with LSP for Rust.
What's the value proposition of NeoVim? I believe they did a code cleanup but I'm not maintaining either project, and they had async execution before Vim, but Vim 8 has that now too.
Maybe I'm just old and grumpy... 😂
That was pretty much my intent behind the question 😀 I was all geared up to move until Vim 8 brought in async exec as well. The code cleanup could in theory lead to less bugs due to weird interactions etc. (and it seems that’s been the case for some people), but I haven’t come across any bugs that affect my workflow, so that too is only a theoretical benefit.
I thought maybe being able to write in plugins in non-vimscript languages (which I believe neovim supports) would be a big one, but no one seems to have mentioned that so maybe not that either.
That's a good point, I actually have had Vim crash on me a number of times in my day job. Usually with way-too-many buffers open. My workflow has evolved into a bit of a monster I guess lol.
As for non-VimL plugins, is that distinct from existing vim support for Python and Ruby scripting?
@digital_carver @Ademan @vim i had the exact same thoughts not so long ago. Vim8 has pretty everything.
I switched to nvim for 2 reasons
1. Vim fugitive had some problems with vim8, something with Gdiff as I remember
2. I switched to zsh and I have vim mode there and the cursor changes depending on mode, but this behavior was incorrect in vim8, the cursor were always the same regardless the mode
There are also some plugins working only in nvim
Most of times it's about Lua config files and some bugs, even if "bugs happen" everywhere.
@vim @digital_carver it just works™
i've moved because of some vim bug related to undo files that's fixed in neovim