11–17 of 17 posts
Earlier quoted context omitted.
That assumes that all the plugins are installed via Git, right?
It updates only those plugins that are installed as git submodules yes. Most recent bundles have git repos, but if they don't https://github.com/vim-scripts mirrors all plugins hosted on vim.org as clonable repos.
Not arguing with his main points, but updating submodules for pathogen is easier than he says. To update submodules do (in the "main dir" of the git repo): git submodule foreach git pull
Question: is there an equally easy way to delete submodules? They're easy as pie to add, and you rightly point out that they are easy to update, but I never figured out an easy way to remove them. I was likely missing something, though.
Interesting. I just recently started using Pathogen, and it is a great improvement, but I do agree that updating plugins is still a chore. How well does Vundle work in Windows? And how does it organize the plugins?
1. add a repo:
$ git remote add remote-vim-surround https://github.com/tpope/vim-surround.git
$ git subtree add --prefix=vim/bundle/vim-surround remote-vim-surround master
$ git subtree pull --prefix=vim/bundle/vim-surround remote-vim-surround master
Not arguing with his main points, but updating submodules for pathogen is easier than he says. To update submodules do (in the "main dir" of the git repo): git submodule foreach git pull
Post author here. You're dead on about this. I could try to turn this into another reason why git + pathogen is lacking as a plugin management system (you have to know a lot about git!), but that is weak, so a better tack is to just agree. Question: is there an equally easy way to delete submodules? They're easy as pie to add, and you rightly point out that they are easy to update, but I never figured out an easy way…
For example to add the rails plugin I can do:
braid add git://github.com/tpope/vim-rails.git bundle/vim-rails