From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] screen-4.6.2-3 (test)
Date: Tue, 23 Apr 2019 04:16:00 -0000 [thread overview]
Message-ID: <1b858b0f-ea27-466a-5d7a-14da99f2322b@shaddybaddah.name> (raw)
In-Reply-To: <announce.uglbbehdsj29muf90ph1a8mo7fdu2a3e3h@4ax.com>
Hi,
On 16/4/19 11:40 pm, Andrew Schulman wrote:
> screen-4.6.2-3 is now available as a test release in Cygwin. This release
> includes a small change to the default /etc/screenrc, that has been
> reported to fix a screen corruption problem that some users - okay, Shaddy
> :) - have reported after detaching from screen[1,2].
Many thanks for this :-) Sorry I went silent in the subsequent
discussion. I became busy, then went travelling for a week. I'll test
this release. Report back.
Whilst I'm at it, I'm not sure if others were able to reproduce. But the
steps to reproduce for me were really quite simple. In mintty, hit enter
a few times to get the prompt off of the top (and create a bit of
terminal history for mintty to restore), just run a screen session
(simple 'screen' command line is sufficient). Hit enter at the new
session prompt a few times so that the cursor is a few lines down from
the top. Type exit (or ctrl-d to detach) and see the message:
[screen is terminating]
at the top, with the original mintty prompt flashing intermixed with the
restored terminal history.
--
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
prev parent reply other threads:[~2019-04-23 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 13:41 Andrew Schulman
2019-04-23 4:16 ` Shaddy Baddah [this message]
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=1b858b0f-ea27-466a-5d7a-14da99f2322b@shaddybaddah.name \
--to=lithium-cygwin@shaddybaddah.name \
--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).