Skip to content
Browse files

document AddonsBisect, rename VAMBisect to AddonsBisect

  • Loading branch information...
1 parent 436dbe9 commit e621b4e210819682d62452ccd237b5889e48aedc @MarcWeber committed
2 autoload/vam.vim
@@ -468,7 +468,7 @@ command! -nargs=* -complete=customlist,vam#install#UpdateCompletion UpdateAddons
command! -nargs=0 UpdateActivatedAddons exec 'UpdateAddons '.join(keys(g:vim_addon_manager['activated_plugins']),' ')
command! -nargs=* -complete=customlist,vam#install#UninstallCompletion UninstallNotLoadedAddons :call vam#install#UninstallAddons([<f-args>])
-command! -nargs=* -complete=customlist,vam#install#BisectCompletion VAMBisect :call vam#install#Bisect(<f-args>)
+command! -nargs=* -complete=customlist,vam#install#BisectCompletion AddonsBisect :call vam#install#Bisect(<f-args>)
function! s:RunInstallHooks(plugins)
for name in a:plugins
9 doc/vim-addon-manager-additional-documentation.txt
@@ -67,6 +67,15 @@ AddonsInfo {id/name} ... *:AddonsInfo*
Shows addon information. Accepts both VAM script names and
script numbers.
+AddonsBisect *:AddonsBisect*
+ Bisect activated plugins to find the one causing some trouble you're
+ experiencing. Bisectng means deviding the list of activated addons
+ into two equal sized sets, then asking you to test whether the
+ issue occurs, then repating the test on either set until one plugin
+ is left.
+ This may not work no Windowsn yet due to the ! usage.
3.2. Functions *VAM-functions*
2 doc/vim-addon-manager-getting-started.txt
@@ -52,6 +52,8 @@ WHY VAM?: ~
- some Windows support
- is not too shy telling you that alternatives exist (and which one)
- copes with "subdirectories contain vim runtimepath" cases
+ - addon bisecting support: Find out which plugin is causing kind of pain to
+ you (|AddonsBisect|)
1. Intro *VAM-intro*

0 comments on commit e621b4e

Please sign in to comment.
Something went wrong with that request. Please try again.