Curious which plugins you needed to disable.
I disabled the following plugins:
- flash - can’t stand ‘/’ search being broken and 30+ years of using ‘s’ to substitute. The problem with “jump search” plugins is that when you type something that doesn’t match every character typed is interpreted as normal mode leading to random commands. Horrid.
- mini.indentscope - seemed to cause slow down navigating and scrolling through code.
- noice.nvim - it’s experimental and it broke command line :%s/search/replace plus some other command line weirdness. I much the traditional command line vs a goofy popup anyway.
My criticism of all vim distros and indeed LazyVim in this instance is including plugins that are highly experimental or plugins that break long standing vi/vim behaviours.
Even if it is trivial to disable a plugin it does create an issue of “discovery” as it’s not always obvious what plugin is responsible for the undesirable behaviour.
That grievance aside, LazyVim is very transparent with its configuration and there is no lock in to any particular set of plugins or plugin configuration. In that respect LazyVim is a clean starter config and still strikes a good balance vs boostraping nvim from scratch.
The thing I always consider is can I refer to any particular plugin documentation and apply it as described. Does my nvim distribution create its own special configuration “levers, settings and overrides” which has lots of magic and pre-canned defaults with limited overrides but still a lot of things that cannot be changed.
LazyVim is the only distribution I found other than bootstrapping myself that didn’t fall into the configuration tar pit.
