From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] handling SIGWINCH with qemu -nographic
Date: Tue, 16 Oct 2007 15:04:52 +0100 [thread overview]
Message-ID: <20071016140452.GA31811@miranda.arrow> (raw)
In-Reply-To: <471410B1.3030703@gmail.com>
On Mon, Oct 15, 2007 at 06:15:29PM -0700, Jeff Carr wrote:
> For those that might not be familiar with SIGWINCH, supporting it
> would allow qemu -nographic to tell when the terminal is a different
> size than 80x24.
That would need support on the remote side (the getty) as well as on the
terminal (minicom/tip/qemu -nographic/whatever).
While this would be a nice feature (and support for propagating the
TERM, LANG and LC_* variables might be nice, too), I'm doubtful as to
whether this will ever happen.
--
Stuart Brady
next prev parent reply other threads:[~2007-10-16 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 1:15 [Qemu-devel] handling SIGWINCH with qemu -nographic Jeff Carr
2007-10-16 2:32 ` Paul Brook
2007-10-16 18:21 ` Jeff Carr
2007-10-16 20:51 ` Stefan Weil
2007-10-16 21:21 ` Paul Brook
2007-10-20 0:24 ` Rob Landley
2007-10-16 14:04 ` Stuart Brady [this message]
2007-10-20 0:22 ` Rob Landley
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=20071016140452.GA31811@miranda.arrow \
--to=sdbrady@ntlworld.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).