Re:Mini.nvim Is Now on Tangled
by canelonesdeverd on Sunday November 15, 2026 @07:58PM
(#50512734)
I'd say its more about the size/scope of each plugin rather than the number, and that you can use the whole thing like an nvim distro or pick and choose what you like and bring them to your own config
Re:Mini.nvim Is Now on Tangled
by eikenberry on Sunday November 15, 2026 @08:01PM
(#50512754)
I think the mini part is that each is fully independent and you can pick and choose which to use individually. I currently use 4 mini.* plugins out of 10 and am happy with what they do.
Not everyone needs the same 4 plugins as you and this is a very nice set of plugins, each parsimoniously designed to have minimal configuration needed. The whole repo is a few megabytes.
The author is a neovim core contributor and I find his approach to plugins very compelling.
A side note is that nvim does incorporate things upstream natively.
I believe "gcc", a la tpope, is now default part of nvim (not as a plugin just as a thing).
Also treesitter.
Even package management is built natively into nvim now (and nvim's implementation is supposedly inspired by mini's).
Same author iirc
The way I read it, it's not that your whole configuration/setup is minimalistic when using this plugin in whole, or some of its parts, but it's rather than each plugin, separately, is reasonably small and self-contained, not aiming to cover absolutely every feature.
By using mini.nvim, I've been able to reduce significantly the number of separate plugins here and there, for example, because the plugins are either sufficient for me, or are reasonably easy to extend in your own config.
It's a great plugin/set of plugins overall. I would not read too much into the name, though.
I am looking at my vim config with my 4 plugins.
What's "mini" about your "45+ independent Lua modules" ?