On 16/02/09 17:06, Ben Fritz wrote:
>
>
> On Feb 15, 3:29 am, Tony Mechelynck<[email protected]>
> wrote:
>
>> Method II
>> ---------
>> 1. Make sure that "D:\Program Files\vim\vim72" (without the quotes) is
>> part of your PATH, which IIRC is a semicolon-separated list. How to set
>> the PATH varies between versions of Windows; on XP it is (IIRC) in
>> "Control Panel => System => Advanced => Environment variables" (or, if I
>> didn't RC, somewhere not too far from that).
>
> This step is probably unneccessary. Every gvim installer I have found
> will automatically place batch files in C:\WINDOWS\system32 (already
> in your path) with names like gvim.bat, vim.bat, etc.
>
>> 2. Start a Dos Box (for instance by invoking cmd.exe in the Execute item
>> of your Start Menu). You may keep that Dos Box constantly open, it is
>> very useful. Start gvim from the command-line, as (e.g.)
>>
>> gvim.exe filename.ext
>>
>> or even without a filename if you want it to open on its "splash screen"
>> without editing an existing file.
>>
>
> You can (and should) omit the ".exe" from gvim.exe to allow the
> automatically placed batch files do their thing.
When I was on Windows, I always directly invoked the binary, with no
noticeable ill effects.
Best regards,
Tony.
--
There's nothing wrong with America that a good erection wouldn't cure.
-- David Mairowitz
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
