Question 1

How do I lazy-load a plugin with lz.n when I use a specific key mapping?

Accepted Answer

Use the 'keys' field in the plugin spec to define the key mapping, and lz.n will defer loading until that key is pressed. For example, specify keys = {"<leader>ft"} for NeoTree, and the plugin loads only when you trigger that mapping, as shown in the examples.

Question 2

lz.n or lazy.nvim: which should I choose for Neovim?

Accepted Answer

Choose lz.n if you want a lightweight, focused lazy-loading library that works with any plugin manager. Opt for lazy.nvim if you need a full plugin manager with features like automatic updates, dependency resolution, and a UI. lz.n is simpler but requires more manual setup.

Question 3

Does lz.n work with Neovim's built-in package manager?

Accepted Answer

Yes, lz.n is designed to integrate with Neovim's native packpath. You can use it with vim.cmd.packadd or the experimental vim.pack in nightly, as detailed in the README's configuration and examples sections.

Question 4

How to handle plugin dependencies in lz.n?

Accepted Answer

lz.n doesn't have a built-in dependencies field. Instead, use the before or after hooks to manually load dependent plugins via trigger_load(). However, the README recommends fixing upstream plugin issues rather than relying on this, as it can be error-prone.

Question 5

Can I lazy-load colorschemes with lz.n?

Accepted Answer

Yes, but you must explicitly specify the colorscheme name in the 'colorscheme' field of the plugin spec. Unlike some managers, lz.n doesn't automatically detect or load colorschemes, requiring manual configuration for each one.

Question 6

How to split my plugin configurations into multiple files using lz.n?

Accepted Answer

Call load() with a module name (e.g., 'plugins'), and lz.n will automatically merge specs from that Lua module and its sub-modules. For instance, store specs in lua/plugins/*.lua, and they'll be combined, as explained in the 'Structuring Your Plugins' section.

lz.n

What is lz.n?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions