This is the mail archive of the
mailing list for the Cygwin project.
Re: screen on 64-bit mangles mintty/buffer
- From: Andrew Schulman <schulman dot andrew at epa dot gov>
- To: cygwin at cygwin dot com
- Date: Mon, 12 May 2014 12:46:26 -0400
- Subject: Re: screen on 64-bit mangles mintty/buffer
- Authentication-results: sourceware.org; auth=none
- References: <5370E144 dot 4010905 at shaddybaddah dot name>
> This is a problem that I noticed some time last year, so I apologise for
> sitting on it for so long. I actually started drafting a number of
> emails to report but never committed.
> The problem only occurs with screen on 64-bit Cygwin. The 32-bit appears
> to work correctly. The problem is that when screen is run in mintty, it
> seems to exclude the bottom line, reducing the actual size of the
> buffer. Further, something goes awry at the top. So that if you run
> emacs -nw or less from within, scrolling via the keys acts very
> If you detach or simply exit the screen session, the problem carries on
> on the mintty you are left with.
> You can resolve this by resizing the window (and back). Everything then
> returns to normal.
> It is interesting to me that the problem also occurs if I ssh into the
> 64-bit Cygwin install via Putty. However, the problem only occurs from
> within the screen session. When you detach or exit, the original Putty
> session/buffer is uncorrupted.
OK. This sounds like the same problem as:
Actually that report is sort of the opposite problem: all of the
scrolling is down in the bottom line. But it sure sounds like the same
The details of what people report vary. For me, scrolling ends up all
down in the bottom line, and resizing the window doesn't fix it.
I also see the problem only in 64-bit. It works fine in 32-bit.
I have found one reliable workaround, at least for me: The problem only
happens if I start screen from my .bash_profile. If I start it from the
command line, it works fine. I don't know yet why that is, but it's a
clue. Probably an environment difference.
Are you using the latest screen release, 4.2.1? Please send output of
> My foolishness in not reporting this as soon as I detected it is that
> my attempts to bisect/rollback to a period where my recollection
> suggests the problem did not exist, have not succeeded. In other words,
> my tests indicate this has been around since screen was built and
> released for 64-bit Cygwin.
> I was hoping to understand the terminal handling and suggest a fix, but
> it is a little bit beyond my capability at the moment. Any help would
> be appreciated (I usually quarantine one mintty which I use for managing
> a handful of screen sessions to work around the problem).
No problem, thanks for reporting. Corinna suggests that it's a mintty
problem. Is that more likely than a screen problem? I don't know. If
it is a screen problem, I don't have the skills to offer a fix - all I
can do is report it to the screen-users list.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple