Sane Vim Plugin Management with Vundle

Not arguing with his main points, but updating submodules for pathogen is easier than he says.<p>To update submodules do (in the "main dir" of the git repo):<p><pre><code> git submodule foreach git pull</code></pre>

I truly prefer to use git-subtree with pathogen.<p>1. add a repo:<p><pre><code> $ git remote add remote-vim-surround https://github.com/tpope/vim-surround.git </code></pre> 2. git-subtree:<p><pre><code> $ git subtree add --prefix=vim/bundle/vim-surround remote-vim-surround master </code></pre> 3. occasional updates:<p><pre><code> $ git subtree pull --prefix=vim/bundle/vim-surround remote-vim-surround master </code></pre> The advantage of this method is that I can keep my config directory in git, pull it onto a new machine, and not have to update any submodules. It's just all there.

Interesting. I just recently started using Pathogen, and it is a <i>great</i> improvement, but I do agree that updating plugins is still a chore.<p>How well does Vundle work in Windows? And how does it organize the plugins?

Updating your plugins (when using pathogen) is super-easy if they're stored in git somewhere.<p><pre><code> Dir.glob("#{ENV['HOME']}/.vimbundles/*").each do |d| next unless File.directory?(d) puts "updating #{d}" `cd #{d}; git pull --rebase; cd -` end </code></pre> in ruby, would be easy enough in bash/zsh/python/perl/ as well.<p>see also: <a href="https://github.com/hashrocket/dotmatrix/blob/master/bin/vimbundles.sh" rel="nofollow">https://github.com/hashrocket/dotmatrix/blob/master/bin/vimb...</a>

It baffles me how underdeveloped the git-submodule command is. I've never enjoyed that aspect of Vim bundle management, and this looks like a refreshing alternative.<p>Is submodule-based package management gone for good? I'm going to wait and see.<p>One thing is clear: the author understands the current Vim ecosystem and knows exactly what pain points still exist. He doesn't diminish how great Pathogen is but has come up with a way to make package management seamless, and for that reason, I'm going to give this a try.

I'm using pathogen with 'braid' to manage git based bundles.<p>For example to add the rails plugin I can do:<p><pre><code> braid add git://github.com/tpope/vim-rails.git bundle/vim-rails </code></pre> then I can do `braid update bundle/vim-rails` to update just that or `braid update` to update all

I've been using (and loving) vim-update-bundles for about 5 months now. I'm not sure how the two compare in terms of features, but the core functionality is the same.<p><a href="https://github.com/bronson/vim-update-bundles" rel="nofollow">https://github.com/bronson/vim-update-bundles</a>

I switched to using Vundle this morning (before seeing the article). It is an excellent way to manage VIM plugins.

<i>...There is a grow­ing con­sen­sus about Vim users that Pathogen is the best way to man­age scripts. The idea behind pathogen is a fan­tas­tic one (to be hon­est, all of Tim Pope’s scripts are well-thought out and exe­cuted; pathogen being no exception)...</i><p>You can get past the "Javascript required" message by disabling CSS (e.g. Web Developer Toolbar extension).