Sane Vim Plugin Management with Vundle(charlietanksley.net)
charlietanksley.net
Sane Vim Plugin Management with Vundle
http://www.charlietanksley.net/philtex/sane-vim-plugin-management/
9 comments
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 to remove them. I was likely missing something, though.
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.
That assumes that all the plugins are installed via Git, right?
I truly prefer to use git-subtree with pathogen.
1. add a repo:
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
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?
How well does Vundle work in Windows? And how does it organize the plugins?
The plugin author discusses that here: https://github.com/gmarik/vundle/wiki/Vundle-for-Windows.
Updating your plugins (when using pathogen) is super-easy if they're stored in git somewhere.
see also: https://github.com/hashrocket/dotmatrix/blob/master/bin/vimb...
Dir.glob("#{ENV['HOME']}/.vimbundles/*").each do |d|
next unless File.directory?(d)
puts "updating #{d}"
`cd #{d}; git pull --rebase; cd -`
end
see also: https://github.com/hashrocket/dotmatrix/blob/master/bin/vimb...
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.
Is submodule-based package management gone for good? I'm going to wait and see.
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.
Is submodule-based package management gone for good? I'm going to wait and see.
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.
For example to add the rails plugin I can do:
For example to add the rails plugin I can do:
braid add git://github.com/tpope/vim-rails.git bundle/vim-rails
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.
https://github.com/bronson/vim-update-bundles
https://github.com/bronson/vim-update-bundles
I switched to using Vundle this morning (before seeing the article). It is an excellent way to manage VIM plugins.
...There is a growing consensus about Vim users that Pathogen is the best way to manage scripts. The idea behind pathogen is a fantastic one (to be honest, all of Tim Pope’s scripts are well-thought out and executed; pathogen being no exception)...
You can get past the "Javascript required" message by disabling CSS (e.g. Web Developer Toolbar extension).
You can get past the "Javascript required" message by disabling CSS (e.g. Web Developer Toolbar extension).
To update submodules do (in the "main dir" of the git repo):