From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] The recent patch "redraw screen upon sigwinch"
Date: Mon, 23 Mar 2009 09:25:40 -0700 [thread overview]
Message-ID: <1237825275-sup-6509@entry> (raw)
In-Reply-To: <1237822979-sup-3515@ausone.inria.fr>
Reformatted excerpts from nicolas.pouillard's message of 2009-03-23:
> I just pulled 'next' and I got a problem with this patch. I run sup in
> a screen and pull that screen through ssh on another machine with
> another screen device. With this patch sup seems blocked, CTRL-C
> unfreeze it, I answer no to the question, and then I can't do a
> CTRL-L.
Yeah, I have the same behavior. I thought I had tested this but I guess
not. I've reverted the branch and remerged into next.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-03-23 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 15:45 Nicolas Pouillard
2009-03-23 16:25 ` William Morgan [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=1237825275-sup-6509@entry \
--to=wmorgan-sup@masanjin.net \
/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