Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<4151F57C.BB4F6EB6@dessent.net>
Date:	Wed, 22 Sep 2004 14:58:20 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: problem with cygwin box (termcap?)
References:	<200409221956 DOT i8MJusA06757 AT panix1 DOT panix DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

David Arnstein wrote:

> I launch a cygwin "box" (command window) on my Windows 2000 machine.
> I run ssh to connect to a shell account running a variant of BSD Unix.
> 
> Whenever I use the program "less" on that shell account, it complains
>         "WARNING: terminal is not fully functional."
> Another user has stated that tin (the news reader) complains
>         "tin: Terminal must have clear to end-of-screen (cd)
> I suspect that these issues are related.  Can the termcap entry for
> cygwin be improved?  Or is this truly a limitation of the cygwin box?

You could also just use rxvt instead of of a cmd.exe window, which
should result in $TERM being set to "rxvt" which should be recognised
everywhere.  If for whatever reason you must use cmd.exe then follow the
advice already in the thread to add the "cygwin" terminal info to the
database on the remote end.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -