From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Re: *spoke to soon to a* Workaround to screen writing over restored buffer on detach/exit
Date: Tue, 09 Apr 2019 06:07:00 -0000 [thread overview]
Message-ID: <6cc3bc5e-2c3c-61a1-8473-8c531faceac7@shaddybaddah.name> (raw)
In-Reply-To: <56fced2e-4f98-7bba-136b-5eeded34ce6f@shaddybaddah.name>
Hi,
On 9/4/19 3:37 pm, Shaddy Baddah wrote:
> I confirmed this by turning off the default "login" mode for a new
> session, which averted attempts to manage utmp entries, and therefore
> avoided the "utmp slot not found" message. I did this by launching a
> session via:
>
> screen -ln
>
> You can also set login off in your .screenrc.
>
> Doing this, screen session plays nicely now. Probably, the error in utmp
> should be actually fixed, or permanently turned off if not workable in
> Cygwin. But for now, I'm so relieved to be able to workaround a daily
> pain in the proverbial.
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.
--
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
next prev parent reply other threads:[~2019-04-09 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 5:37 Shaddy Baddah
2019-04-09 6:07 ` Shaddy Baddah [this message]
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
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=6cc3bc5e-2c3c-61a1-8473-8c531faceac7@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).