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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=TEKqgdkacEwEwzgZOamw2xjhq71UHtJdW3ClN/Je3UG
	uvKEIujESlHe0l0Z+rMez5+pUy4g/4ufDI2Djfo0NzZwfeQSAKz8SQMzch0GkTBM
	qvpeZU3bVjiNfL9tLQnT6nnwUtVYGCEb3iTvtsr+Ep+dmaCZnKpqZ2905Tm7LSlU
	=
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:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=CZSslsPFFf4DhGmMillvBp3bFBY=; b=A6MsBmf0/2KGDXHtj
	fuf5U/kIriGVLYM/pf5GXYjfOWlYtOhcqQndjXm2N2foX3+5IWbs6qAms8cdLFk1
	r3EqzgRpagezqvnt3JAMyznyVpLlkaNGBz4lvCsnSGcH2Nx4b6ObXa4a9IvH8nDJ
	G2pXydtTfm2PVyMR/9c7AJJ4Rg=
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=0.1 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_HELO_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	moutng.kundenserver.de
Message-ID:	<5298F8CE.6090606@towo.net>
Date:	Fri, 29 Nov 2013 21:27:58 +0100
From:	Thomas Wolff <towo AT towo DOT net>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: bug in 'cs' value of Xterm termcap (was: Updated: screen 4.1.0-20130513-1)
References:	<1385590460 DOT 84148 DOT YahooMailBasic AT web181501 DOT mail DOT ne1 DOT yahoo DOT com>
In-Reply-To:	<1385590460.84148.YahooMailBasic@web181501.mail.ne1.yahoo.com>
X-TagToolbar-Keys:	D20131129212757901
X-IsSubscribed:	yes

Am 27.11.2013 23:14, schrieb matthew patton:
> 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.

The ts/fs/ds entries are a trick to mimick the window title as a pseudo
"hard status" line. cs is the "scrolling region".
Not understanding your report completely (what is the -1 and -2
releases?), it could be that some application (maybe screen itself?)
uses cs in the wrong way which produces exactly the described effect. I
noticed myself recently that this can happen if cs is assumed to be just
\E[%i%d;%dr without the %p1,%p2 items, which is kind of weird. Anyway,
does it happen in a fresh terminal, then screen, then ls, or did you run
any other applications before the bug occurs?
------
Thomas


--
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 -