Disable plugins from the :Lazy screen

[m-fonseca]

I recently had a problem I was trying to debug, and wanted to start removing plugins to see which one was causing my problem. Perhaps theres an easy way to do this that I don't know of (and couldn't find), but an easy way to disable plugins from the :Lazy screen could be quite useful (especially if there are a lot of mods).

Its already designed to be able to individually install and update individual plugins, and it seems natural to also have a disable/enable individual plugin as well from the same place.

Just an idea anyway.

[folke]

Just add enable=false to the plugins you want to disable. Not going to add anything else for this

[abeldekat]

I created lazyflex.nvim. The plugin facilitates the enabling/disabling of multiple plugins using a few well-chosen keywords.

[bhogan-bdai]

How does one add "enable=false"? it's not in the modal, and if not there, which file?

[dpetka2001]

It's mentioned in the Plugin spec. The key is enabled.

[torimus]

Just add enable=false to the plugins you want to disable

Did you mean enabled option, mentioned in Plugin Spec? Your didn't worked on the first try.

Why this handy feature is not considered to be included in lazy.nvim's menu? Possible issues with reloading environment after selective enabling/disabling of particular plugins? Now you have to find the plugin declaration file, edit the option in, and eventually re-install related plugins. Cumbersome..

[rektide]

This kind of sucks, because as for example an AstroVim user, it's not really me bringing in plugins: my community packs bring in a lot of plugins too. Just finding where a given plugin is located, in order to disable it, is quite challenging at times.

I wish Lazy could help me debug my modules, by letting me disable a plugin temporarily, in a top down fashion, rather than making me go bottom up to find where each plugin is and disable it on-site. This would be so useful for trying to isolate & understand which modules are causing problems, which currently there's not a great way to do.

[diego898]

Really wish this was an option - you can do so much from the :Lazy screen...update, (delete!), inspect, even view a diff... a key for "toggle" or "enable" etc. would fit nicely.

[cpachmayr]

Just an up-vote on this as a feature --- latest updates broke the editor --- and I just presumed I could disable from the Lazy screen since that's where I enabled them.

[pencilcheck]

It is actually very easy, just move everything to a folder and that's it. lazy matches on the folder based on the first level, unless you explicitly included in your lazy init those in nested folders wouldn't be loaded at all.

E.g. If you setup to do this in your lazy

-- load plugins
require("lazy").setup({
  {
    "NvChad/NvChad",
    lazy = false,
    branch = "v2.5",
    import = "nvchad.plugins",
  },

  { import = "plugins" },
}, lazy_config)

You should have a folder called "plugins" under "lua"
You can separate each pluigin in a file, so your plugins folder look like this

/016   alpha.lua
/017   auto-session.lua
/014   init.lua
/015   lspconfig.lua
/013   oil.lua
/019   rooter.lua
/018   zellij-nav.lua

Then create a folder like "disabled" in the plugins folder, and move all the relevent plugins files you want to disable into that folder and that's it.

[torimus]

That's anything but "easy" in comparison with the original request, ie. enable/disable plugins on-the-fly, from within an editor.

[aptdnfapt]

[aptdnfapt]

ma god...