Temporarily disable some plugins using pathogen in vim.

前端 未结 5 680
青春惊慌失措
青春惊慌失措 2020-12-12 11:43

I think I have a bug in one plugin. I would like to load only this plugin, without having to delete all the other bundles in my pathogen\'s bundle folder, to debug.

5条回答
  •  一整个雨季
    2020-12-12 12:07

    The easiest method to disable a plugin when you use Pathogen is by adding it's bundle name to the g:pathogen_disabled variable, before starting pathogen.

    So an example from my own vimrc

    " To disable a plugin, add it's bundle name to the following list
    let g:pathogen_disabled = []
    
    " for some reason the csscolor plugin is very slow when run on the terminal
    " but not in GVim, so disable it if no GUI is running
    if !has('gui_running')
        call add(g:pathogen_disabled, 'csscolor')
    endif
    
    " Gundo requires at least vim 7.3
    if v:version < '703' || !has('python')
        call add(g:pathogen_disabled, 'gundo')
    endif
    
    if v:version < '702'
        call add(g:pathogen_disabled, 'autocomplpop')
        call add(g:pathogen_disabled, 'fuzzyfinder')
        call add(g:pathogen_disabled, 'l9')
    endif
    
    call pathogen#infect()
    

    Update: Another method, supported by Pathogen, is to simply rename the directory for the bundle you want to disable so that it ends in a tilde (~). So to disable the autocomplpop bundle, simply rename it to autocomplpop~.

提交回复
热议问题