-
-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New module] lazy.nvim #797
Comments
I kinda guess that reinventing the wheel in this case is pretty much appropriate |
@ehsan2003 there was a fairly long discussion about this in #421, and the general consensus was basically "lazy.nvim already does this and we can use it to try out the idea at first and then eventually roll our own", but obviously there's merits to doing this ourselves. If you have any insights feel free to leave them in the original feature issue |
I've started experimenting with creating a plugin manager for lazy.nvim. I've taken the current packer.nix implementation as inspiration as I am not that familiar with the internals just yet. Constructive criticism welcome! |
I've added a PR for adding lazy.nvim as an alternative to packer. Still draft until some other folks give it a spin. Please feel free to give it a spin! |
@pta2002 I guess we can close this now since the new plugin has landed... |
You're right! |
Plugin: lazy.nvim
Plugin repository: https://github.com/folke/lazy.nvim
Is the plugin on nixpkgs: Yes
Extra information
Following the discussions around #421, one thing has become clear: lazy.nvim already implements pretty much everything we need.
Therefore, instead of reinventing the wheel, the best course of action starts with adding a module to allow for plugin management via
lazy.nvim
. This can later be implemented to load plugins fromextraPlugins
, but at first it can just be a separate option from the module, given that supporting that would require a flag to tell nixvim to not install plugins the other way.Either way, this should follow the same general idea as the packer module. Since
lazy.nvim
supports loading plugins from a directory (via thedir
option), we can sidestep its plugin downloading completely, too, keeping the config reproducible :) (Though we should still allow a user to havelazy.nvim
download plugins, in order to let them easily install out-of-tree plugins. However, IMO everything officially supported by us should come from Nix, since it's not that much extra work to package).Eventually™ we can fork out lazy.nvim's lazy-loading code to a separate library, and have a module for that, to make builds smaller. But as I said in the beginning, no need to reinvent the wheel for now! Let's just use what works and see how it goes.
The text was updated successfully, but these errors were encountered: