I love the fact that you don’t have to call setup() to use it. It means that if you are happy with the defaults, the plugin is truly lazy-loaded (I’ve checked, there is no plugin directory that would get loaded automatically).
Otherwise my approach is to find particularly simple plugins and reading their code. :) I’m mainly focusing on lua-based plugins. It’s certainly not any harder than vimscript plugins, and much easier in some cases.
I love the fact that you don’t have to call
setup()to use it. It means that if you are happy with the defaults, the plugin is truly lazy-loaded (I’ve checked, there is noplugindirectory that would get loaded automatically).Really excited with all of the cool stuff people are doing with neovim plugins. I just wish it was easier to onboard learning new plugins!
Do you mean learning how to build new plugins?
I’ve been spending a bit of time learning this myself, this thread was a good starting point: https://www.reddit.com/r/neovim/comments/wxbnk8/whats_the_best_practice_for_developing_neovim/
Otherwise my approach is to find particularly simple plugins and reading their code. :) I’m mainly focusing on lua-based plugins. It’s certainly not any harder than vimscript plugins, and much easier in some cases.