X-Spam-Check-By:	sourceware.org
Message-ID:	<43EAFC07.1A72F3E8@dessent.net>
Date:	Thu, 09 Feb 2006 00:23:35 -0800
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Looks like some terminfo data is not correct
References:	<43EAF8ED DOT 3070608 AT ptc DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
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

Alex Shturm wrote:

> If my TERM variable is set to either "cygwin" or "rxvt", after I exit
> from VI the contents of the window gets restored.
> If TERM is "xterm", it does not get restored.
> The same behavior is observed in both cmd-based window and in rxvt window.
> 
> Looks like a bug in "terminfo" data for "xterm" terminal.
> 
> Can anybody confirm this behavior?
> If this is a confirmed bug, is there a workaround?
> Will it be fixed in the future?

That's to be expected.  The setting of TERM has to match the type of terminal
that is in use.  A CMD.EXE window is not an xterm, which is why it has its own
terminfo entry called "cygwin".  The two have different characteristics.  If you
lie to the app and tell it that it's running in a certain type of terminal when
in reality it's not, then you get all kinds of strange things happening.  It
would only be a bug if when you were *using* xterm and had TERM=xterm and
noticed that the screen was not restored.

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 -