3 ms·
Yeah it's a tough one. I've switched back and forth relatively freely over the years, but now that new VimScript (vim9 script) has breaking changes and neovim
by freedomben 4y ago
Yeah it's a tough one. I've switched back and forth relatively freely over the years, but now that new VimScript (vim9 script) has breaking changes and neovim will not be supporting it, it's probably time to pick a pony.
I may end up sticking with og vim but my heart has always been with neovim. regular vim would undoubtedly still be stuck in the stone age (including with no :terminal) had neovim not started some competition. I get the feeling that VimL's evolution was done in a way that made it quite difficult or impossible for neovim to merge/rebase into. Hopefully that wasn't intentional.
- yoyohello13 4y agoThe creator of Neovim's LSP integration is currently working on a VimL9 JIT compiler to make Vim9 plugins work for Neovim (early stages). So you still may be able to stay on the fence.
- alwillis 4y ago"Exciting progress on vim9script => Nvim-Lua transpiler”: https://twitter.com/Neovim/status/1575455161186664451 https://twitter.com/Neovim/status/1575455161186664451
- alwillis 4y agoVim has had :terminal since version 8.1 [1]. [1]: https://gist.github.com/mahemoff/8967b5de067cffc67cec174cb3a9f49d https://gist.github.com/mahemoff/8967b5de067cffc67cec174cb3a...
- maxnoe 4y agoThe whole reason there ever was a vim 8 was neovim and the pressure it applied to implement async plugins and terminal. Without neovim, we'd still be on vim 7.xxxxx
- freedomben 4y agoGoing somewhat off memory here, but my recollection is that was like 3 or 4 years after neovim's first release.
- alwillis 4y agoThat’s true.