Bram, in the end I am happy to go with your decision, however your
haven't convinced me yet... so one last go.
I've had a look at lots of directories under Program Files on my
Nearly all have their uninstall.exe / unwise.exe in a sub-directory
named Uninstall, System or Setup.
Those that don't have a postfix.. something like setup_wm.exe (Windows
Media Player) or unins000.exe.
I said nearly all - there is one exception I've found so far that had an
uninstall.exe in with the other
So maybe a beter name would be inst_vim.exe and un_vim.exe (or
something like that). It is still very
I believe you are under-estimating the problems the batch files might
cause - though I've only one reportable
incident - which is that the .cmd file was truncating the command-line
when I was passing a few dozen files to the command line. (So not hugely
a problem for the most part).
If only winnt handled symbolic links properly (like if shortcuts could
I personally don't care about cr/lf conversions. Everything works event
if it doesn't happen.
From: Bram Moolenaar [mailto:Bram@...
Sent: Friday, 6 September 2002 7:14 AM
To: Michael Geddes
Subject: RE: Patch for nsi fileset when creating windows installer from
Michael Geddes wrote:
> Or make the windows zip file consistent with the other archive by
> the docs &c into the runtime directory? Is there a reason they aren't
The Unix archives are setup to be able to run "make install". The
MS-Windows archives are setup to use the files right after unpacking.
> Still, if somebody more familiar with the installer than I am could do
> the detecting, that would be great.
There are more issues to be taken care of, such as LF to CR-LF
translation. That would be enough to say "just use the PC archives", if
it weren't for patches. And the files obtained from CVS also use the
Unix layout and line separators. Sounds like a script is needed to make
a copy of the tree to be able to run NSIS.
> Also, is there any reason why the installer doesn't distribute the
> command-line version of vim? It is very useful for batch processing
> (some of my scripts assume its presence too).
- It adds to the size of the package.
- Not many people are expected to use the console version.
- There are actually several console versions for different systems (Win
9x and NT/2000/XP). Would have to include at least two.
> Could we at least have the patches to dos_inst.c as this allows me to
> more easily make my own distribution for work where this behaviour is
> Another option could be to choose a different name for the .exe - for
> example viminst.exe & vimunins.exe - would this be more palatable?
I don't like either solution, because it is so common to type "install"
or click on "install.exe". I think you will just have to move these
executables elsewhere if you insist on adding this directory to your
FATHER: You killed eight wedding guests in all!
LAUNCELOT: Er, Well ... the thing is ... I thought your son was a lady.
FATHER: I can understand that.
"Monty Python and the Holy Grail" PYTHON (MONTY)
/// Bram Moolenaar -- Bram@...
/// Creator of Vim - Vi IMproved -- http://www.vim.org
\\\ Project leader for A-A-P -- http://www.a-a-p.org
\\\ Lord Of The Rings helps Uganda - http://iccf-holland.org/lotr.html