On Sat, 2007-03-17 at 00:03 +0100, A.J.Mechelynck wrote: > > Sure. But you don't _have_ to source it. Since 15 June 2006, you can > use instead > > :UseVimball /temp
Tony, you convinced me to try again. But I feel vindicated, again I experienced the same kind of issues I always seem to have. :UseVimball ./ produced for me: -------------------------- $ ls -R1 ./* ./netrw.vba ./autoload: netrwFileHandlers.vim?[[[1 netrwSettings.vim?[[[1 netrw.vim?[[[1 ./doc: pi_netrw.txt?[[[1 ./plugin: netrwPlugin.vim?[[[1 ./syntax: netrw.vim?[[[1 -------------------------- These are the filenames, folding brackets and all! This is with netrw 108 JUST downloaded from Dr. Chip's site in the default gVim of the Fedora Core 6 distribution. It has dumped it all over my $HOME, despite being located in it's own subdirectory. (At least with Cream, which follows cwd, it does unpack where the file is.) > BTW, a common format for distributing zipfiles is a self-extracting > .exe -- like, for instance, your own Vim installers. Just to be clear, the Cream installers are actual programs not self-executing "zip files". We use the Nullsoft Scriptable Install System (NSIS), a mature software dedicated to installation on Windows. > I suppose I needn't point out that an .exe can potentially do > anything to your Windows system that your permissions allow it to do Very true... > -- not that I expect anything evil from you, Steve, quite the > opposite. But the concept can quite arguably be described as broken > and much less obvious than a simple .zip. I respectfully disagree. A .tgz/.zip is about distributing a simple file structure, an .exe installer is about installation, a far more complex concept. Just read through the Cream installer build script: http://cream.cvs.sourceforge.net/cream/misc/gvim.nsi?view=markup it is doing a lot more than a zip file could ever do. (And, to my original point, needs to do.) -- Steve Hall [ digitect dancingpaper com ]
