Re: Which Win Vim is which?

On 3/3/2010 10:22 AM, Steve Hall wrote:
> From: Bram Moolenaar, Tue, March 02, 2010 10:09 am
>
>> I would very much appreciate if the installer does everything that the
>> "old" MS-Windows installer does. Then we can finally get rid of the
>> consoles popping up.
>>
> Unfortunately the default Vim installer has one "feature" that the
> Nullsoft installer can not perform: command line operation.
>
> The current GUI Vim installer is actually a combination of two
> different installers, a Nullsoft GUI wrapper around a custom binary
> command line utility. The popups are caused by the Nullsoft portion
> calling the command line one. There's no way around them without
> completely abandoning the command line utility.
>
> I'm still a little vague as to why a command line installer is useful
> on Windows, a platform never intended to have a terminal interface in
> the first place. And for anybody who insists on installing in a
> Command Prompt, they ought to know enough about Vim to install it
> without a program, after all, you just copy the files and fire off a
> .reg or two. (Which is all an installer does anyway.)
>
Server Core 2008 R2 might be a good argument on behalf of a command line
installer. But recreating what is in the command line utility shouldn't
be that bad in Nullsoft regardless. Could you then just use the NSIS
command line arguments to do a command line based install? One
installer with two modes, no gui required?

>> The Gvim installer deserves some modernizing. But we still have people
>> working in a console, thus we need to be able to type "vim file" and
>> have the installed vim.exe executed. There might be something else that
>> a few users need.
>>
> I can appreciate this, having a command line version of Vim still has
> plenty of purpose. That's why I am considering re-including it in the
> Cream + Vim installer. Even though most Cream users probably won't
> care, it would ensure the Cream version supplies all the functionality
> that our non-Cream installer has.
>
Yep, maybe even a bit of a resurgence with mysisgit (git) and powershell
gaining a bit of traction.

>> We also need to make sure everything works under Windows 7. I ran into
>> some problems myself but haven't found time to look into it.
>>
> I don't have access to this platform yet, so any testing would have to
> be by others. Windows always was pretty good about backwards
> compatibility though, and Nullsoft claims compatibility with 7, so I
> don't expect any problems with our installer.
>
> (Anybody here use a Cream-generated gVim installer on Windows 7 that
> can report?)
>
I got about 8 or 9 installs on Windows 7 - x64/x86 Professional and
Windows 7 - x64/x86 Ultimate, and the only issue I have run into is some
problems with the right-click menu options (missing).

--
Robert Melton | Contact Information @ http://robertmelton.com/contact

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php