From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: bug in 'cs' value of Xterm termcap (was: Updated: screen 4.1.0-20130513-1)
Date: Fri, 29 Nov 2013 00:26:00 -0000 [thread overview]
Message-ID: <pgmf99tut34rit1vqdtvd5vlf4j5deepbb@4ax.com> (raw)
In-Reply-To: <1385590460.84148.YahooMailBasic@web181501.mail.ne1.yahoo.com>
> 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
next prev parent reply other threads:[~2013-11-29 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 22:14 matthew patton
2013-11-29 0:26 ` Andrew Schulman [this message]
2013-11-29 20:28 ` Thomas Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pgmf99tut34rit1vqdtvd5vlf4j5deepbb@4ax.com \
--to=schulman.andrew@epa.gov \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).