X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:mime-version
	:content-type; q=dns; s=default; b=KbrarLzs9Dx+gDMyFbeMc74tkYOaM
	k+3nwzMxPcTmQQp99KHYtXoRnA0tDPXSqaEOEfCi21M399UrQ1Jw/UDGjpo09r7U
	7OgtsZeJnFMBEiYTi15W7InvZFA3vBUXm1PU6piwZdFCyiCySTIbAhhG9Ciy7Vln
	OeTBK/0E4IcWBg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:mime-version
	:content-type; s=default; bh=1D8MUlJw0qKc5KI8XN1LHQ3umdU=; b=NMx
	6+5dLtlqQJtAmAOqUPWc6Fv6l5Zk8ZIlPl4zyM+pIeALQJKY+mhlGfuKTI/BBz1w
	or4KgaUxSZLe3BgbiuiO94KZ33embJLzZOgcxSXy/0xZfkYp+rUfoMFSefQoRPIT
	T7f2dZY/+hZmLw7Nkzr/+VWs0GyLWNTDMmfRSSVU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=2.3 required=5.0 tests=BAYES_60,FREEMAIL_FROM,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	nm26-vm7.access.bullet.mail.gq1.yahoo.com
Message-ID:	<1385590460.84148.YahooMailBasic@web181501.mail.ne1.yahoo.com>
Date:	Wed, 27 Nov 2013 14:14:20 -0800 (PST)
From:	matthew patton <pattonme AT yahoo DOT com>
Subject:	bug in 'cs' value of Xterm termcap (was: Updated: screen 4.1.0-20130513-1)
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0

For whatever reason I set my newly installed environment to use 'xterm' mode and ran across this bug.

The archives led me to
http://www.cygwin.com/ml/cygwin/2013-07/msg00029.html
and specifically

# Set the hardstatus prop on gui terms to set the titlebar/icon title
> termcapinfo xterm*|rxvt*|kterm*|Eterm*|cygwin hs:ts=\E]0;:fs=\007:ds=\E]0;\007

and wanted to mention that with both the -1 and -2 releases, even with the 'termcapinfo' override in the above post the hardstatus and caption lines end up 1 line off the bottom IFF $TERM=xterm be it in an honest to goodness X11 xterm or the windows terminal. This causes everything to fail to properly scroll. Once a single screen worth of output is sent, everything just gets put on the last line. This obviously is not a good thing.

However if $TERM is any of 'cygwin', 'xterm-vt220', 'xterm-256color', 'vt100', or 'vt220' it works just fine since the offending 'cs' stanza is never set like below.

termcap  xterm|fptwist hs@:cs=\E[%i%d;%dr:im=\E[4h:ei=\E[4l
terminfo xterm|fptwist hs@:cs=\E[%i%p1%d;%p2%dr:im=\E[4h:ei=\E[4l

In my ~/.screenrc it was sufficient to use

termcapinfo xterm* cs

to restore correct behavior. Unfortunately I haven't a clue what the various escape sequences mean.

As a side note I think it would be a good idea to wrap all termcap|info lines with single quotes at least for consistency.


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

- Raw text -