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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Dfm2VgVO7iAnWjNO
	09FeOGJ+Vm5gvFf/RfSXL7RhJ6MV0NCxtIVymNndYBIy/dogFwb/NziGlqdQUCUK
	mL+/y/QOwE+QhmNVX1TzKwXxZUEVBD4ixQT3sj2nnmiFURXM9AZJjauEjS7WCNYO
	T/enEDVfxvCR4PuFmTxahHIJBfc=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=i4yFzrNlPClAtpA+5XHTOy
	E7W9M=; b=e7UXo6o7dgpHHmKQe09hvjYeqZ1XpdgZkw6roXlnt1Pr/D20d/deoh
	k2qeidBGCMlvF7Zd7/Ha1hxxJScYiPhW3IIi37Gi7aNPHNO3Y9tEzrpY5/WZTx/r
	8InFnQ5kKuK4Y9/ZSEsFZAoQpZg8nT8G09OW6x9mY/BOgfYJHQcHk=
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.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1876, 11.04.2019, 11042019, screens
X-HELO:	mout.kundenserver.de
Subject:	Re: *cause of* screen writing over restored buffer on detach/exit
To:	cygwin AT cygwin DOT com
References:	<56fced2e-4f98-7bba-136b-5eeded34ce6f AT shaddybaddah DOT name> <6cc3bc5e-2c3c-61a1-8473-8c531faceac7 AT shaddybaddah DOT name> <b0290101-3511-9ffb-91d3-e88afdbe9df1 AT shaddybaddah DOT name> <990saedodb302s3fr7me8j2befc9pdam97 AT 4ax DOT com> <fdbb0b82-f47d-3eb9-ed81-7d6765258b8f AT towo DOT net> <sjbuae1shfd44i6beomlm5prhkr37hadtf AT 4ax DOT com>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<b0f04efc-2bf0-3860-11fd-6c6664543bd9@towo.net>
Date:	Thu, 11 Apr 2019 19:24:17 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version:	1.0
In-Reply-To:	<sjbuae1shfd44i6beomlm5prhkr37hadtf@4ax.com>
X-IsSubscribed:	yes

Am 11.04.2019 um 14:12 schrieb Andrew Schulman:
>> Am 10.04.2019 um 17:04 schrieb Andrew Schulman:
>>> Hi Shaddy. There you go again.
>>>
>>>> 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 don't know whose fault the problem is either, but it's probably a
>>> particularity of Cygwin. So I'm happy to package the fix as long as it
>>> doesn't create any problems.
>> screen sends CSI ? 1049l on exit which restores the cursor to the
>> position where it was previously saved.
>> It's the "te" (not ti) terminfo sequence for xterm on cygwin.
> Thomas, can you please clarify: Are you suggesting changing ti to te in the above entries?
I was just reporting what I had discovered. The above settings do not 
seem to make sense, though, as they would restore the cursor (to what?) 
when screen is started.
On the other hand, screen behaviour when the settings are disabled do 
not make much sense, either. It sends a Restore Cursor sequence without 
having sent a Save Cursor before. Very weird.
> Or do you have another suggested patch?
Any change I tried seems to make screen exit behaviour better, sometimes 
leaving at the bottom, sometimes at the top (after clearing the screen).
>
> Although I'm the screen maintainer, I've never learned the intricacies of termcapinfo.
The screen manual is a bit fuzzy about this. Apparently you can tweak 
screen's assumptions about your terminal. But normally you shouldn't 
need to.
Thomas

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