Hi,

 For the real vim junkie there are several sources for the "real
 stuff" ( == newest versions of vim/scripts/plugins et cetera
 available).

 I myself use to update my vim source with the newest patches and
 download the runtime files on a regular base. Furthermore I download
 the newest CVS stuff from vim-ruby, the ruby support files for vim.

 The vim-ruby files go into ~/.vim/....
 The runtime files go into /usr/share/vim/vim70 (== $VIMRUNTIME)
 The result of the compilation of the sources go also to $VIMRUNTIME
 (and non-scripts to other places).

 I recognized, that some files are doubled: Older version of the
 vim-ruby support files go also to $VIMRUNTIM.

 Furthermore: Newly installed vimruntimefiles will be overridden with
 older ones from the compilation results of the vim sources (when a
 new patch is available...).

 As it seems with this practice of trying to have always the newest
 vim stuff on my hd I will shoot into my own feet...

 If vim recognized a script file which it has already loaded from
 another place, will it be loaded ?

 Has vim an automatism to load the script with the highest versioning?

 How can I simplify the update of my whole vim environment without the
 need to look into each single file whether it is newer/older as
 another file of the same name at another place and what version of
 this file will work with what version of another file of the same
 suit at shat place?

 Keep hacking!
 mcc


 

Reply via email to