I use VIM for code development and lot of things. I see that there are lot of scripts, configurations shared at vim.org/scripts, also some at github. Time to time I would like to check which one of the scripts used by me were improved. This would need either manual checking of the scripts, but I am too lazy to do that. Writing some code to do the checking and upgrading is also an option, but I am not sure whether there is any agreement what all script contributors always follow. I would like to have a upgrader for these scripts. Is there any solution, or any practice for maintaining the VIM scripts?
+1
A:
I use pathogen.vim to make updating scripts stored on github trivial. Put pathogen.vim in .vim/autoload and add call pathogen#runtime_append_all_bundles() into your .vimrc file to set up pathogen. Then in .vim/bundle, I git clone [vim plugin], and updating is as simple as a git pull in the appropriate directories.
kejadlen
2010-01-16 17:04:16
Thanks! Tim Pope made a good job, not only with pathogen but other vim scripts as well. http://github.com/tpope
fifigyuri
2010-01-17 19:30:26
This answer may be incomplete for some systems - http://www.adamlowe.me/2009/12/vim-destroys-all-other-rails-editors.html (note `filetype off` on top)
skalee
2010-08-01 19:36:04
It is great that VIM supports such a thing by default, but I checked some of my scripts and they do not support GetLatesVimScripts sadly.
fifigyuri
2010-01-17 18:33:03
+1
A:
If you are using ubuntu linux, you can install the vim addon manager: sudo apt-get install vim-addon-manager
David Ruan
2010-01-19 08:42:52