On 07/03/09 18:46, Gary Johnson wrote:
> On 2009-03-07, Tony Mechelynck wrote:
>
>> However, what's wrong with running native-Windows
>> versions of Vim and gvim, such as those from
>> https://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721
>> ? (Click the clipboard-like icon to see what was compiled-in.)
> The advantages to using Cygwin's vim rather than Windows' vim (not
> gvim) is that Cygwin terminals such as rxvt are more versatile than
> the Windows console (although you can get third-party Windows
> consoles, too) and that from Cygwin's vim you have access to a
> Unix-like environment any time vim needs the OS or a shell.
>
> I tried for a while to use Windows' gvim with Cygwin's shell but
> found too many cases where it just didn't work quite right. For
> example, some Cygwin commands will return the full path names of
> files such as
>
> /usr/local/src/foo
> /cygdrive/c/bar
>
> and native-Windows gvim can't find them.
>
> Regards,
> Gary
To pass a Cygwin-like path to a Windows-like application, you have to
process it first via cygpath (see "man cygpath"). That's what the
vim72/src/make_cyg.mak does to compile (with Windows Perl) the
if_perl.xs module required by the Perl interface.
What I recommend if you want to run Vim within Cygwin but don't want the
trouble of running an X-server on top of Windows, is to use the Console
version of Cygwin vim. When I was on Windows, I used Cygwin a lot, but
not exclusively, and I used Cygwin vim (started from Cygwin bash),
Windows vim (started from cmd.exe) and Windows gvim (started from
cmd.exe or from a desktop shortcut), as the need arose.
Best regards,
Tony.
--
Crash programs fail because they are based on the theory that, with
nine women pregnant, you can get a baby a month.
-- Wernher von Braun
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
