public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: *cause of* screen writing over restored buffer on detach/exit
Date: Thu, 11 Apr 2019 17:24:00 -0000	[thread overview]
Message-ID: <b0f04efc-2bf0-3860-11fd-6c6664543bd9@towo.net> (raw)
In-Reply-To: <sjbuae1shfd44i6beomlm5prhkr37hadtf@4ax.com>

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

  reply	other threads:[~2019-04-11 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09  5:37 Workaround to " Shaddy Baddah
2019-04-09  6:07 ` *spoke to soon to a* " Shaddy Baddah
2019-04-10  3:18   ` *cause of* " Shaddy Baddah
2019-04-10 15:04     ` Andrew Schulman
2019-04-10 17:12       ` Thomas Wolff
2019-04-11 12:12         ` Andrew Schulman
2019-04-11 17:24           ` Thomas Wolff [this message]
2019-04-10 20:03     ` Thomas Dickey
2019-04-10 21:51       ` Thomas Wolff
2019-04-11 23:06         ` Thomas Dickey
2019-04-11 23:50           ` Thomas Dickey

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=b0f04efc-2bf0-3860-11fd-6c6664543bd9@towo.net \
    --to=towo@towo.net \
    --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).