Steve Hall wrote:
From: Charles E Campbell Jr, Fri, March 16, 2007 12:17 pm
Please try netrw v108l which I just put on my website:
http://mysite.verizon.net/astronaut/vim/index.html#NETRW
Unfortunately these appear distributed in vimball format only.
It is unrealistic to expect users to fire off a home-brewed executable
simply to unpackage TEXT FILES!
Age-old formats like tar.gz or .zip are still around precisely because
they allow user control--simple inspection and evalutation without
potentially modifying system files.
Steve, pease simmer down. The vimball format is actually a text format. Also,
in recent versions, instead of sourcing the vimball you can give a path
argument to the ":UseVimball" command in order to unpack the vimball any which
where you damn well please.
See ":help :UseVimball".
As for a "home-brewed executable", the Vim 7.0.0 executables from the official
Vim site are good enough for the task; and your own (non-Cream) distributions
wouldn't be "home-brewed" to the lambda Windows user anyway.
Here is how to avoid "modifying system files": Since there is a test at the
start of the netrw scripts to avoid double sourcing, you can test them by
unvimballing them under $VIM/vimfiles, $HOME/vimfiles or $HOME/.vim, without
removing the older files under $VIMRUNTIME (I know the latter is contrary to
Dr. Chip's recommendations, but it works). You will just have to watch out and
remove the "user versions" of the scripts if and when the normal Vim upgrade
process installs a newer version under $VIMRUNTIME.
Best regards,
Tony.
--
How doth the VAX's C-compiler
Improve its object code.
And even as we speak does it
Increase the system load.
How patiently it seems to run
And spit out error flags,
While users, with frustration, all
Tear all their clothes to rags.
