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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=iSMXhI9HGK1BzUlwZ1lYCIAhdUk8DSqESMEMAr1EbgD6ezrIm4Arr 2gsv59w7lk+BtB66xX0QVCniUq/Jmd2AVct2APa2Klz3yqYD+zzUQDcA5CPhIAHm s8XRB0hfQY09UERHACiKZXWa9Nt6R+4i8y4C9/jDx+rB0PtEiwWCVI= 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:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=z0qwr1nfBJV9JrSBMl9WMUY3Ah4=; b=u2igLySkEo0KPKykNUynBOzSw4Xs myWmbafG22Xa0wle7BI64kt3pcsanY9qTKYAYXzL04xmsecphyI1UotxqiKPNNDD L8HCp/v8RWaESw+39HdEsDPYuYGPa1DOt/cS7T23Folirb8GV9ZKqJO54dY95pu8 AMDgmdxyKqJe0Ys= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.7 required=5.0 tests=AWL,BAYES_80,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: bug in 'cs' value of Xterm termcap (was: Updated: screen 4.1.0-20130513-1) Date: Thu, 28 Nov 2013 19:25:49 -0500 Lines: 41 Message-ID: References: <1385590460 DOT 84148 DOT YahooMailBasic AT web181501 DOT mail DOT ne1 DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > 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. Matthew, thanks for reporting that. So far I'm not able to reproduce it. Normally I have TERM=xterm-256color outside of screen. I reset it to TERM=xterm and started a new instance of screen, and although I set the hardstatus line, I can't find any problems with scrolling. Does anyone else observe this problem? What's the proposed solution? Remove the two lines you cited above? See http://cygwin.com/ml/cygwin/2013-10/msg00369.html for another recent screen scrolling issue that I couldn't reproduce. > 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. I also mostly don't have a clue what the escape sequences mean, although I've looked up a few of them when I had to. Mostly that's deep terminal magic, and I don't mess with it, just pass on what comes from upstream or I'm otherwise told is needed. Andrew -- 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