option to disable auto download pathogen.

[t9md]

pathogen itself can be loaded from ~/.vim/bundle directory. so I hope vim-update-bundles support option to disable downloading pathogen into ~/.vim/autoload/ directory.

Here is excerpt from pathogen's README.md's FAQ section.

Q. Can I put pathogen.vim in a submodule like all my other plugins? A. Sure, stick it under ~/.vim/bundle, and prepend the following to your vimrc:

source ~/.vim/bundle/vim-pathogen/autoload/pathogen.vim

[bronson]

I agree. It sounds like an easy modification.

How would you autodetect this? Presence of a ~/.vim/bundle/vim-pathogen directory?

[t9md]

Thanks.

How would you autodetect this? Presence of a ~/.vim/bundle/vim-pathogen directory? Current vim-update-bundles assume bundle dir located on bundle_dir = "#{config[:vimdir_path]}/bundle". so, autodetect is simple I think.

But another strategy(execution order) change is seem to good for future maintainability(ex: support option to specify bundle dir name).

• Current execution order
  1. download pathogen to ~/.vim/autoload/pathogen.vim.
  2. update bundle and docs
• New execution order
  1. update bundle
  2. download pathogen to ~/.vim/autoload/pathogen.vim. if pathogen is not managed with vim-update-bundles.
  3. update doc

[bronson]

Shoot, this is such a good idea that I'm thinking vim-update-bundles shouldn't install Pathogen at all. It'll just print a warning if your .vimrc doesn't specify a Pathogen bundle.

Besides, I always wondered how vim-update-bundles would keep the Pathogen script up to date... This fixes that.

[bronson]

Hope that makes it easy to support tplugin, see Runtime Path in the README.

If you try it, please file an issue! I'd like to include instructions for using tplugin in the Runtime Path section too.

[t9md]

Thanks, good update! this update greatly help new Vim user start using other's configiration which use Vundle.