Sane Vim Plugin Management with Vundle
charlietanksley.net
Sane Vim Plugin Management with Vundle
1–10 of 17 posts
Re: Sane Vim Plugin Management with Vundle
#2How well does Vundle work in Windows? And how does it organize the plugins?
Re: Sane Vim Plugin Management with Vundle
#3 Dir.glob("#{ENV['HOME']}/.vimbundles/*").each do |d|
next unless File.directory?(d)
puts "updating #{d}"
`cd #{d}; git pull --rebase; cd -`
end
in ruby, would be easy enough in bash/zsh/python/perl/ as well.see also: https://github.com/hashrocket/dotmatrix/blob/master/bin/vimb...
Re: Sane Vim Plugin Management with Vundle
#4You can get past the "Javascript required" message by disabling CSS (e.g. Web Developer Toolbar extension).
Re: Sane Vim Plugin Management with Vundle
#5To update submodules do (in the "main dir" of the git repo):
git submodule foreach git pullRe: Sane Vim Plugin Management with Vundle
#6Is 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.
Re: Sane Vim Plugin Management with Vundle
#7Re: Sane Vim Plugin Management with Vundle
#8Not 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
Re: Sane Vim Plugin Management with Vundle
#9Re: Sane Vim Plugin Management with Vundle
#10Not 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
That assumes that all the plugins are installed via Git, right?
https://github.com/vim-scripts
mirrors all plugins hosted on vim.org as clonable repos.