Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I should have mentioned that if you use and enable the semi-official treesitter plugin. Neovim has treesitter built-in, which is a proper parser written in C. Vim uses regexes, which is slow and error prone. Treesitter is usually much faster. Treesitter is also much better at languages-within-languages, like code blocks in markdown.
For folks wondering why more neovim users (including me) are out there. Please check the Vision of Neovim, which pretty much aligned with what I wanted when vim became only editor of daily use. And maybe that is also the reason it aligns with most people and why they started / switched to neovim. Plus, (personally), I hate Vimscript. It's complicated and I even felt to write my own language than writing in Vimscript. Moreover, they came up with Vimscript 9.0 now after so long time and with a Warning! That's just lame.
I guess that I sort of did actually answer your question: there are plugins that work on Neovim but not on Vim, but the only plugin I found that worked on Vim but not on Neovim is vim/killersheep, so you get more plugins at no cost.
It has been a "planned feature" for the last 8 years (https://github.com/neovim/neovim/issues/1496).
I relied heavily on https://github.com/LunarVim/Neovim-from-scratch to get setup (I had to be humble and follow it step by step) - my config - https://github.com/ADGEfficiency/dotfiles/tree/master/nvim
I relied heavily on https://github.com/LunarVim/Neovim-from-scratch to get setup (I had to be humble and follow it step by step) - my config - https://github.com/ADGEfficiency/dotfiles/tree/master/nvim
I'm a staunch vim user for multiple decades and I can't believe I'm saying this but I'm moving to neovim. I'm liking having a meta alt-key that seem to always work, a builtin lsp, virtual text, treesitter, all features included in compilations, and while I can deal with Vim 9 script and I'm not a lua expert but I like lua and being able to use lua rocks package manager via packer is attractive too. This might be a good time to make this decision as once I start writing more in Vim 9 script it'd be more of a hassle to rewrite configuration for neovim later. I adore and owe much to Bram's contributions obviously but this thread with people trying to convince him to consider virtual text and failing was the clincher for me. Despite understanding his point, I like that neovim is more willing to accept these kind of features. Anyway if I end up not liking it, there's always plain vim to fall back on and it's far from the worst case scenario.
Hello, I'm Jorengarenar and this is my Darkness
A core contributor to Neovim is toying with a Vim9Script to Lua convertor.