Convenient way to disable plugins for debugging? Separating lazy.nvim config from its bootstrapping?

[rieje]

Disclaimer: noob.

• Is there a way to conveniently disable (not uninstall) plugins for debugging Neovim config or to configure config structure to improve in this regard? E.g. a list of all plugins and commenting out or adding in a single line mentioning the name of the plugin. Right now I have a plugins/ directory where I would comment out the entire file. I see there's disabled_plugins but I tested by adding which-key.nvim and it does not seem to work so I assume it's only for Neovim builtin plugins.

• I have a bootstrap.lua where it includes the code for boostrapping and also:

  require("lazy").setup({
  { import = "my.plugins" }},
  {
  root = vim.fn.stdpath("data") .. "/lazy", -- directory where plugins will be installed
  defaults = {
  lazy = false, -- should plugins be lazy-loaded?
  version = nil,
  -- version = "*", -- enable this to try installing the latest stable versions of plugins
  },
  -- ... etc.

Is there a better way to abstract lazy.nvim settings than dumping them to a file in plugins/ and then passing it as a table to the second argument of require('lazy").setup assuming that works? I think it might be more appropriate to define the bootstrapping code and the code for configuring lazy.nvim since lazy.nvim is itself a plugin. For example, I would consider { import = "my.plugins" }}, to be part of the bootstrapping process but not the settings for lazy.nvim. Interested in any other ways that make could make it more apparent that lazy.nvim is both a plugin manager and a standard plugin itself by the way of structuring it as code.

Much appreciated.

[folke]

You can set cond=false for a plugin you want to disable.