From: greggj AT savvis DOT com (Gregg Jensen)
Subject: Re: elvis & vim, was Re: Does anyone have a man command??
1 Apr 1997 18:25:13 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <3.0.1.32.19970321085014.009906f0.cygnus.gnu-win32@mail.savvis.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: greggj AT mail DOT savvis DOT com
X-Mailer: Windows Eudora Light Version 3.0.1 (32)
Original-To: ap096 AT po DOT cwru DOT edu
Original-Cc: gnu-win32 AT cygnus DOT com
In-Reply-To: <199703311354.IAA16140@ns2.harborcom.net>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

At 08:56 AM 3/31/97 +0000, Kevin Dahlhausen wrote:
>
>> The 'vi' like editor 'elvis' can read man, and i found 'elvis-2.0' for
>> win32. Unfortunately
>> it isn't buil on cygnus-win32 distrib, so it can't handle unixlike
>> pathnames !!! 
>> I tryed to port it with the tiny termcap embeded, and with gnu libtermcap.
>> It compile quite
>> easily in both case, and it runs, but input seems to be 'frozen' (in fact
>> keystrokes seems
>> to be bufferised). Anybody has an idea ??
>
>I tried to build a native GNU-WIN32 version of the VI clone VIM.
>It compiled but exhibited the same behavior -that is the program 
>started, displayed 'Empty Buffer' and completely locked up.  I 
>haven't gotten any further on this yet.   Since both ports show the 
>same problem, maybe this points to a problem in the termcap 
>code?

As a point of interest, I am a xvile (another vi clone that has an
X windows interface) user when on a unix box.  And, after I pulled
down the X libraries, referenced on this list recently, I pulled the
latest (x)vile sources down to my NT box and started compiling.  I
made two adjustments (at the configure stage and one line change in
one file) and it popped out with a clean compile.  I started it up,
verified that it worked and am using it now.  My hats off to the 
cygnus-win32 group.  

Gregg Jensen
(oh, I am currently using eXodus X server, not the free one mentioned 
here before.)

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".