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:	<200012011656.LAA23060@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:	Cygwin termcap entry for Solaris
Date:	Fri, 1 Dec 2000 11:54:43 -0500
MIME-Version:	1.0

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?

Thanks,
Steve


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

- Raw text -