- Joined
- Apr 1, 2024
The git version of neovim has its own plugin manager. You will have to build it yourself, or use a distro that has a precompiled one.What with ol' Bram passing on and all, I've been trying to move on to neovim after about two decades of heavy vim usage. But my word, neovim's plugin situation is even worse than vim's. It's so bad that everywhere just tells you to use a plugin manager. What a pile of dogshit! Makes me seriously consider Emacs. Any other vi-heads out there with suggestions of better solutions? I use like 5% of vim's features and all I want out of this is rainbow delimiters for Scheme hacking: https://github.com/HiPhish/rainbow-delimiters.nvim
Basically, any shitty vi clone with rainbow parens will work.
But if you came from normal vim you can just use pack like a lot of people do on normal vim, and you can still configure it in vim script.
Overall I think using lua is more flexible, and the better option. It's completely optional, unless you are using a plugin manager that requires lua like lazy.
Or if you truly have an aversion to having a plugin manager do the work for you, you can git clone the plugin and put it in the runtime path then set it up the way it says to, to actually use it.
Emacs doesn't really solve any of the issues I see people having with vim/neovim, and just throws it's own on top. Like being slow, single threaded, and even more bloated. While still having all the plugin nonsense, and needing even more configuration to get to a state a vim user would be happy with.

