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
	:content-type:content-transfer-encoding; q=dns; s=default; b=OPY
	xbXQr7qFJn1p9Bn7CvMjL8uQfLCT1IjxDAiU5frZw5u+6T2t2flMPLWBu3UTr9H+
	T86Si6iggL5x8Pf7YpnB1jkTaQHKGio3END7jcCJto1wvGX3LRn59tpRsjwgAQ/k
	mkrAL6tmBp3vMktyZifMBWZtRV112WhWcwWjd3Sg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5370E144.4010905@shaddybaddah.name>
Date: Tue, 13 May 2014 00:57:08 +1000
From: Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: screen on 64-bit mangles mintty/buffer
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

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

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.

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

-- 
Regards,
Shaddy

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