-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: How disable a plugin without removing it? #432
Comments
@cjnucette you can prevent plugins from loading by making them Alternatively, if this is something you might want to do a lot you can create a pattern for it, e.g. -- outside of packer startup probably
local function minimal()
return vim.env.MINIMAL == nil
end
packer.startup(function(use)
use {"a/plugin", cond = minimal}
end)
When you start vim and want a minimal init you can run MINIMAL=true nvim |
FWIW there's some discussion around making all plugin opt by default and packer loading them itself, which will make things like creating a minimal init.vim easier to do (see #50) |
Thanks, I'll try this. |
I should also mention that after adding |
You can do this in
vim-plug
by commenting the corresponding line, but withpacker
the plugin is always loaded because is in thertp
, which is not the case with vim-plug. I want to be able to disable some plugins to create a minimalinit.vim
without the need to run:PackerClean
.The text was updated successfully, but these errors were encountered: