Bill McCarthy wrote:
> On Sat 1-Sep-07 1:39pm -0600, sc wrote:
> 
>> again i find myself struggling with netrw
> 
> This may be unrelated to sc's problem, but happened to me in
> my Windows installation.
> 
> I removed all *netrw* files from my $vimruntime and
> installed the latest (112b) there.  It worked fine.
> However, I later updated my runtime files from the ftp site
> (the update only copies new files and only overwrites
> existing files if the ftp file has a newer date).
> 
> After the update, I noticed that I was back to 110.
> 
> Looking around at the ftp site, I noticed that there are two
> very similar versions of the autoload file netrw.vim on the
> ftp site.  One is in the autoload/ directory and starts
> with:
> 
> " netrw.vim: Handles file transfer and remote directory listing across
> "            AUTOLOAD SECTION
> " Date:         Jun 20, 2007
> " Version:      110k    NOT RELEASED
> 
> The other is in the plugin/ directory and starts with:
> 
> " netrw.vim: Handles file transfer and remote directory listing across
> "            AUTOLOAD SECTION
> " Date:         Jun 21, 2007
> " Version:      110
> 
> These two files are identical, except for the differences in
> those lines and the line starting with: let g:loaded_netrw =
> 
> So this second version is getting written to the plugin\
> directory of my runtime files and gives me the version 110
> announcement.
> 
> The netrw.vim file should be removed from the plugin/
> directory of the ftp site.
> 
> A working solution, until this is done, is to create a
> current dated empty file called netrw.vim in the plugin
> directory of your runtime.  That way the rouge netrw.vim

s/rouge/rogue
" this is not about cosmetics, jewellery or Canadian football

> will not be written there when you update your runtime.
> 

On Unix-like systems, rsync (with --delete) will make the destination tree 
identical to the source tree regardless of anteriority, so the above won't 
work there. The following will (after $VIMRUNTIME/plugin/netrw.vim is deleted 
once by hand):

#!/bin/bash
rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/ 
2>&1 | tee rsync.log
rm -vf runtime/plugin/netrw.vim 2>&1 | tee -a rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
make -C src installruntime 2>&1 | tee instrt.log

Notes:
1. In case your mailer or mine added spurious line breaks: the long line 
starting "rsync" includes everything up to but not including the line starting 
"rm".
2. the "vim" step cleans up the log by removing "nonspacing" lines -- 
temporary "progress reports" which were overwritten on the screen
3. the "make installruntime" step only needs to be done when:
   a) there are changed files other than doc/tags and plugin/netrw.vim, and
   b) you aren't about to compile a new patchlevel of Vim (in which case the 
"make install" which follows it will take care of runtime files anyway).


Best regards,
Tony.
-- 
Did you know ...

That no-one ever reads these things?

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui