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:date:from:to:cc:message-id:in-reply-to
	:references:subject:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=IlzrJ77C4fVZ7GxV
	r10dADyVx0YO2NMHhm6uRu5IIFqLZRa5fKJWlXHCzV2FH7woz25DsNF3K37YTh30
	uys2ykcFAzwtAOaF4Ims3HL+RbhmgYYnOj0D8XZKTSHl5VlxvpDIr6r9+jeckpyh
	djbX1/Cn7LkTMNmtGV14yNwT9+E=
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:date:from:to:cc:message-id:in-reply-to
	:references:subject:mime-version:content-type
	:content-transfer-encoding; s=default; bh=oQcuhkGF68jzRN9O6WfXyw
	UGj8o=; b=Cz6dTC52vbV3dvPt8dPkEwSBSRkRU3CSx6K9Fqj7ruQSo+mpgn4LUm
	k2Tc6qcTi5ypjlvGprU6l7P9nQqAPOfGoLaJH3qt6FWNIBWrgu/PCL6p4ThEOeMh
	EXRUoUmaGINEwVbSpBgt4mb+7He/+hXkE0sT7kibo9FiJvfw54+/I=
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-Spam-SWARE-Status:	No, score=-2.4 required=5.0 tests=AWL,BAYES_50,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=osc, Normal, helping, baddah
X-HELO:	smtp-nf-201.his.com
Date:	Wed, 10 Apr 2019 16:03:23 -0400 (EDT)
From:	Thomas Dickey <dickey AT his DOT com>
To:	Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
Cc:	cygwin <cygwin AT cygwin DOT com>
Message-ID:	<1919747550.7813512.1554926603758.JavaMail.zimbra@his.com>
In-Reply-To:	<b0290101-3511-9ffb-91d3-e88afdbe9df1@shaddybaddah.name>
References:	<1554907871 DOT 14124 DOT ezmlm AT cygwin DOT com>
Subject:	Re: *cause of* screen writing over restored buffer on detach/exit
MIME-Version:	1.0

----- Original Message -----
| From: "Shaddy Baddah" <lithium-cygwin AT shaddybaddah DOT name>
| To: "cygwin" <cygwin AT cygwin DOT com>
| Sent: Tuesday, April 9, 2019 11:18:19 PM
| Subject: Re: *cause of* screen writing over restored buffer on detach/exit

| On 9/4/19 4:07 pm, Shaddy Baddah wrote:
|> 
|> This helped with screen when using Putty to a Cygwin ssh session. For
|> some reason, it isn't helping for running screen locally in a mintty
|> session. And it's not mintty either, because I can ssh to a Debian
|> stretch server within mintty and I can use its screen without this
|> issue happening. Back to the drawing board for me.
| 
| I understand the cause of the issue now, by capturing and comparing the
| escape characters used to control the terminal by screen on Cygwin and
| Debian.
| 
| It is not so much the detach/exit is the issue, although the escape
| sequence for Cygwin includes a couple of extra xterm OSC Set Text
| Parameters -> Change Icon Name and Window Title outputs. I misdiagnosed
| this somehow. I can suppress the extra utmp error one of these OSC
| outputs, but it didn't/doesn't really make a difference.
| 
| The issue is in the escape sequences sent to the terminal by Cygwin
| screen to switch to new windows buffer, as compared to Debian.
| 
| Debian uses xterm sequence DECSET / ESC[?1049h in the switch to the new
| window. Cygwin uses the two sequences ESC7 / Save Cursor (DECSC) and
| ESC[?47l / DEC Private Mode Reset (DECRST) -> Use Normal Screen Buffer.
| 
| 
| The reason seems to be that the Debian screen package packages a custom
| /etc/screenrc that does not include this explicit term capability:
| 
| 
| #
| # Do not use xterms alternate window buffer.
| # This one would not add lines to the scrollback buffer.
| termcap xterm|xterms|xs ti=\E7\E[?47l
| terminfo xterm|xterms|xs ti=\E7\E[?47l
| 
| 
| 
| If I comment these out, my screen issue is resolved.
| 
| I'm not suggesting this is a problem with Cygwin screen... it is using
| the upstream settings. In fact, I am not confident to say where the
| fault lies. Perhaps screen is right to use these sequences, but the
| xterms used (putty and mintty) aren't doing the right thing?

yes - that's one of a half-dozen cases where PuTTY has never matched xterm's behavior.

-- 
Thomas E. Dickey <dickey AT invisible-island DOT net>
http://invisible-island.net
ftp://ftp.invisible-island.net

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