Should i use lze if i use lazy.nvim?
#33
|
im currently using lazy.nvim, and im a user not a plugin guy, so should i use this to load plugins after installing them with lazy? or is it supposed to be used by rocks or pckr? |
Replies: 1 comment 10 replies
|
lazy.nvim handles lazy loading, and you can use either nix or lazy.nvim for installing plugins but you need a lazy.nvim spec for it. lze or lz.n are for when you arent using lazy.nvim As long as the plugins are installed in the normal nvim packpath, like via nixCats, or paq.nvim or rocks, lze or lz.n can be used for lazy loading. But lazy takes over like, everything. So, use nixCats and lazy, or just use nixCats and lze EDIT: Just realized which repo this is. You can use paq.nvim or rocks as well, anything that installs plugins on the normal packpath in
And if you override the default load function, it can work with many more. But using lazy.nvim + lze doesnt make sense. Why have 2 things to manage lazy loading when 1 does the job. |
lazy.nvim handles lazy loading, and you can use either nix or lazy.nvim for installing plugins but you need a lazy.nvim spec for it.
lze or lz.n are for when you arent using lazy.nvim
As long as the plugins are installed in the normal nvim packpath, like via nixCats, or paq.nvim or rocks, lze or lz.n can be used for lazy loading.
But lazy takes over like, everything. So, use nixCats and lazy, or just use nixCats and lze
EDIT: Just realized which repo this is.
You can use paq.nvim or rocks as well, anything that installs plugins on the normal packpath in
pack/something/{start,opt}/*will work withlzelzeis extremely flexible. It works by default with ANY plugin manager that allows you to…