help using Vim with gnuwin32 tools?

help using Vim with gnuwin32 tools?

[John Cook]

Hi.

What do I need to do to get Vim working with the gnuwin32 
toolchain (e.g., bash)?  I saw a lot of talk about this in 
the mailing list archives of several months ago, but nothing 
recently.  There are some defined(__CYGWIN32__) in the source 
code (I have vim-5.0p) so it appears that at least some of the 
gnuwin32-specific patches circulating back then have made it 
into Vim, but make ran into problems.  I have the stock b18 
version of the cdk.  Do I need Sergey Okhapin's newer version 
of cygwin.dll or newer versions of anything else?

The 'win32 console' version of Vim works mostly OK, but its 
path handling converts / to \, so (for example) 'vi /.bashrc' 
brings up an empty file unless I happen to be in a directory 
on the root drive.  Also, I'd like to be able to use the 
editor-dependent commands of sdiff with Vim (I set the 
EDITOR variable to point to Vim, but the 'eb' command in sdiff 
brings up an empty file).

I know nearly nothing of termcap and ncurses (sorry!), so if 
I need to acquire and build these, please point me to useable 
sources.  (I do have TERM=linux.)

Thanks,

John
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: help using Vim with gnuwin32 tools?

[Micheal A. Benzinger]

Hi John,

I sent the changes needed to make VIM work with CYGNUS to
Bram Moolenaar who was kind enough to fold these back into
the source master files.  You will also notice that he has
added $(SUFFIX) to the install portion of the Makefile so
that execucatbles created with a .exe can be installed.

VIM seems to compile and work fine with Cygnus' GNUWIN32.
I have Sergey's DLL from the beginning of September.  I will
tell you that color syntax high lighting does not work with
version 5.0p.  If you want color high lighting, get version
5.0o.  I have sent Bram a message about this and have tried
to debug it with limited success.  There's a lot of code there
to digest and understand.  At least I hope I can narrow it
down for him.

By the way, the slash works fine here.  I think you meant to
issue 'vim ./.bashrc'.  For me this will open the file .bashrc
in the current directory.  Since the code is configured with
a UNIX system in mind, it understands the '/' directory
separator.

Mike Benzinger

At 04:50 PM 10/24/97 -0700, John Cook wrote:
>Hi.
>
>What do I need to do to get Vim working with the gnuwin32 
>toolchain (e.g., bash)?  I saw a lot of talk about this in 
>the mailing list archives of several months ago, but nothing 
>recently.  There are some defined(__CYGWIN32__) in the source 
>code (I have vim-5.0p) so it appears that at least some of the 
>gnuwin32-specific patches circulating back then have made it 
>into Vim, but make ran into problems.  I have the stock b18 
>version of the cdk.  Do I need Sergey Okhapin's newer version 
>of cygwin.dll or newer versions of anything else?
>
>The 'win32 console' version of Vim works mostly OK, but its 
>path handling converts / to \, so (for example) 'vi /.bashrc' 
>brings up an empty file unless I happen to be in a directory 
>on the root drive.  Also, I'd like to be able to use the 
>editor-dependent commands of sdiff with Vim (I set the 
>EDITOR variable to point to Vim, but the 'eb' command in sdiff 
>brings up an empty file).
>
>I know nearly nothing of termcap and ncurses (sorry!), so if 
>I need to acquire and build these, please point me to useable 
>sources.  (I do have TERM=linux.)
>
>Thanks,
>
>John
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: help using Vim with gnuwin32 tools?

[Micheal A. Benzinger]

Hi John,

I have supplemental information.  I finally found what
has changed in VIM 5.0p that makes syntax highlighting
not work.  You will find the diff below.

Mike Benzinger

Make the following modifications to "screen.c" and build.

1791a1792
> #ifndef __CYGWIN32__
1810a1812
> #endif

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: help using Vim with gnuwin32 tools?

[Micheal A. Benzinger]

Hi John and the rest of the group,

Well, you can all ignore my previous two mail messages.
After sending the last message it finally dawned on me
what screen.c was trying to accomplish.  I then remembered
that I had doctored the 'md', 'so', etc. codes to produce
color for less, man, etc.  I did a little more digging and
have finally diagnosed the problem.  The termcap implementation
I am using is termcap-1.3, the GNU implementation.  It does
not handle the "%p1" format command that is supposed to
essentially ignore the first argument.  That means when a call
was made to tgoto with the AF code of "\E[3%p1%dm" and 0 and 4
as arguments, the resulting string from tgoto would be
"\E[314m" which the terminal does not understand.  I modified
the code in the termcap, which by the way is distributed with
termcap-1.3, to remove the trailing 1 from the push command.
Low and behold, the color high lighting started to work.

Bottom line for all this, VIM 5.0p works just fine in console
mode, color high-lighting and all.  The problem lies in tgoto.
I am not certain at his point what course of action to take.
Anybody out there have more knowledge of termcap than I do
who can educate me about what to do?  I have O'Reilly and
Associates' book "termcap & terminfo".  The AF command is not
documented in this book.  The %p1 command is poorly documented
at best.  The info files for GNU's termcap-1.3 does not have
any more information either.

Thanks in advance,

Mike Benzinger

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

Re: help using Vim with gnuwin32 tools?

[Earnie Boyd]

I suggest looking at Pete Jordan's debash which you can find at 
http://www.horus.cix.co.uk/downloads.html .  I have been using version  
4.6 of vim on win32 with debash and have little problem finding path 
names.

The problems with path names using debash will come when you try to 
reference a cygwin path from within vim with one of the file operation 
commands.

-        \\||//
---o0O0--Earnie--0O0o----
-earnie_boyd@hotmail.com-
------ooo0O--O0ooo-------

>From: John Cook <john.cook@kla-tencor.com>
>To: "'gnuwin32'" <gnu-win32@cygnus.com>
>Subject: help using Vim with gnuwin32 tools?
>Date: Fri, 24 Oct 1997 16:50:28 -0700
>
>Hi.
>
>What do I need to do to get Vim working with the gnuwin32 
>toolchain (e.g., bash)?  I saw a lot of talk about this in 
>the mailing list archives of several months ago, but nothing 
>recently.  There are some defined(__CYGWIN32__) in the source 
>code (I have vim-5.0p) so it appears that at least some of the 
>gnuwin32-specific patches circulating back then have made it 
>into Vim, but make ran into problems.  I have the stock b18 
>version of the cdk.  Do I need Sergey Okhapin's newer version 
>of cygwin.dll or newer versions of anything else?
>
>The 'win32 console' version of Vim works mostly OK, but its 
>path handling converts / to \, so (for example) 'vi /.bashrc' 
>brings up an empty file unless I happen to be in a directory 
>on the root drive.  Also, I'd like to be able to use the 
>editor-dependent commands of sdiff with Vim (I set the 
>EDITOR variable to point to Vim, but the 'eb' command in sdiff 
>brings up an empty file).
>
>I know nearly nothing of termcap and ncurses (sorry!), so if 
>I need to acquire and build these, please point me to useable 
>sources.  (I do have TERM=linux.)
>
>Thanks,
>
>John
>-
>For help on using this list (especially unsubscribing), send a message 
to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".