From 5a561873ed03dd0c18060a931423575fdb9deb62 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gr=C3=A9goire=20Paris?= Date: Thu, 9 Oct 2014 23:42:46 +0200 Subject: [PATCH] document how to blacklist plugins --- README.markdown | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.markdown b/README.markdown index 5e32dc3f..05d16495 100644 --- a/README.markdown +++ b/README.markdown @@ -62,6 +62,15 @@ and other comma-delimited path options in ways most people will never need to do. If you're one of those edge cases, look at the source. It's well documented. +## Blacklisting plugins + +Want to find what plugin is causing a bug ? Do a bisection by using the blacklist. +You can blacklist plugins by adding them to the `g:pathogen_blacklist` variable. +Make sure you define it before calling `pathogen#infect()`. + + let g:pathogen_blacklist = ['plugin1', 'plugin2'] + call pathogen#infect() + ## Runtime File Editing `:Vopen`, `:Vedit`, `:Vsplit`, `:Vvsplit`, `:Vtabedit`, `:Vpedit`, and