Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<200012011807.NAA06520@darkstar.qx.net>
Sensitivity:	Company-Confidential
From:	Steven Curtis <sjc AT qx DOT net>
Reply-To:	sjc AT qx DOT net
To:	cygwin AT sources DOT redhat DOT com
Subject:	Re: Cygwin termcap entry for Solaris
Date:	Fri, 1 Dec 2000 13:05:23 -0500
MIME-Version:	1.0

Did not mean to post that message twice.  I thought the first one didn't get through.  Anyway, I've tried setting the TERM env var to "ansi" and vi still does not work correctly.  I tried it again just to verify, and it still doesn't work.  I try editing my .login file that has tabs and such, and vi paints characters where there aren't any, and other strange anomalies.  Any other suggestions?

Thanks,
Steve

> 
> From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
> Date: 2000/12/01 Fri PM 12:26:09 EST
> To: sjc AT qx DOT net, cygwin AT sources DOT redhat DOT com
> Subject: Re: Cygwin termcap entry for Solaris
> 
> --- Steven Curtis <sjc AT qx DOT net> wrote:
> > Hello all,
> > 
> > I regularly telnet net from a cygwin terminal to a Solaris box, and have
> > never gotten vi to respond correctly regardless of what I set my TERM env var
> > to.  I've tried vt100, vt220, ansi, and xter.  None seem to work properly. 
> > Lately, I've tried grafting cygwin termcap entries from other Unix machines. 
> > I've tried entries from an OpenBSD machine and a Linux machine, but captoinfo
> > on Solaris never seems to be able to grok the entries.  It complains several
> > times of "Termcap entry is too long" or "termcap code is not a valid name". 
> > The resulting terminfo entries using tic on the output do a better job than
> > adjusting the TERM env var, but they all have different problems.  I'm no
> > termcap guru and couldn't write a valid entry to save my life.  Has anyone
> > found or written a complete and correct termcap entry for a cygwin terminal
> > type that works on Solaris?
> > 
> 
> 1) leave the client side setting CYGWIN.
> 2) after managing to login change TERM to ansi.
> 
> YMMV,
> 
> =====
> Earnie Boyd
> mailto:earnie_boyd AT yahoo DOT com
> 
> ---         <http://earniesystems.safeshopper.com>         ---
> --- Cygwin: POSIX on Windows <http://gw32.freeyellow.com/> ---
> ---   Minimalist GNU for Windows <http://www.mingw.org/>   ---
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Shopping - Thousands of Stores. Millions of Products.
> http://shopping.yahoo.com/
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 
> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -