Charles E Campbell Jr wrote:
Bill McCarthy wrote:
(concerning updating to netrw v102i)
After some struggling to get the .vba file, it installed
nicely in my vimfiles/ directory. It didn't work at all
until I removed the v98 distribution files:
[c:\vim\vim70]zip -rm netrw98 . -i *netrw*
Yes, that's why I said to be sure to remove all vestiges of older
netrw. Netrw
has the common to plugins feature to prevent itself from being loaded more
than once. The vimball installs itself into the first accessible
directories along
your runtimepath; typically, this location is the user's personal
plugins location.
However, the system copy of plugins loads first; thus, the older copy
of netrw
ends up taking precedence if its not removed first.
then it worked fine - but once Bram updates the "official"
plugin directory, I like to have modified versions in my
vimfiles so I can still apply patches to the release and
have my modifications take precedence.
Well, Bram typically doesn't release patches to plugins, syntax files,
indent files,
etc. Whenever vim 7.1 is released, it will install itself into the
vim70 directory,
Correction: it will create a new vim71 directory and install itself
there; anything in the vim70 directory and its subdirs won't be used by
Vim 7.1
and will include a version of netrw. Due to the logic mentioned above,
it will
take precedence over your personal copy of netrw anyway.
[...]
I'm not convinced. When loading plugins (after the vimrc has been run)
they will run in the following sequence:
1) ~/.vim/plugin/*.vim (Unix) or ~/vimfiles/plugin/*.vim (Windows)
2) $VIM/vimfiles/plugin/*.vim
3) $VIMRUNTIME/plugin/*.vim
4) $VIM/vimfiles/after/plugin/*.vim
5) ~/.vim/after/plugin/*.vim or ~/vimfiles/after/plugin/*.vim
When the distributed copy of the plugin is loaded (at step 3) it will
notice the "traffic light" variable created by the upgraded version (at
step 1 or 2) and do nothing. (But if the upgraded version was installed
in $VIMRUNTIME/plugin it would of course be lost when upgrading to 7.1).
Also, this scenario assumes that you restart Vim between installing the
vimball and trying it out.
Best regards,
Tony.
