rffwva
Last Updated: July 05, 2017
·
9.128K
· jan0sch
2aaae7041aca85da930bcaf14d6768d2

Update your vim pathogen plugins.

Because I don't have my whole .vim directory under version control I usually do something like this to update my bundles.

cd ~/.vim/bundle
for i in `ls`; do
  cd "$i"
  git pull
  cd ..
done
Say Thanks
Respond

10 Responses
Add your response

5088
C56883b43d1381943013beccf1abcd2f

you can also use the command

git submodule foreach git pull origin master
over 1 year ago ·
5110
2aaae7041aca85da930bcaf14d6768d2

@telemachus I know of the ls pitfalls but in that case it seems okay because the directory names are usually sane. ;-)

over 1 year ago ·
5111
2aaae7041aca85da930bcaf14d6768d2

@rkrdo But that does only work if you have your whole directory under git control which is not the case here.

over 1 year ago ·
5121
C56883b43d1381943013beccf1abcd2f

@jan0sch true, that command is when you use submodules :p

over 1 year ago ·
13880
2c90565e7c155dd15310869d0396d334

Thanks man! Updating my vim plugins was always so tedious!

over 1 year ago ·
13903
2aaae7041aca85da930bcaf14d6768d2
over 1 year ago ·
14103
48e6672805886d1d3b2eded4fbcce098

I use this script for updating and deleting pathogen submodules http://artmees.github.io/gitsubmodule/

over 1 year ago ·
18731
None

for i in ~/.vim/bundle/*; do git -C $i pull; done

over 1 year ago ·
18742
2aaae7041aca85da930bcaf14d6768d2

@frankbe Very nice one. :-)

over 1 year ago ·
28194
None

do NOT parse output of ls, that's what globs are for. http://mywiki.wooledge.org/BashPitfalls#for_i_in_.24.28ls_.2A.mp3.29

over 1 year ago ·
Filed Under