From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] chardev: add vte chardev
Date: Wed, 13 Mar 2013 15:25:52 +0100 [thread overview]
Message-ID: <51408C70.7010603@redhat.com> (raw)
In-Reply-To: <87k3pbiiur.fsf@codemonkey.ws>
On 03/13/13 13:29, Anthony Liguori wrote:
> Gerd Hoffmann <kraxel@redhat.com> writes:
>
>> Kill the dirty hack which hooks gtk vte initialization into the
>> qemu consoles subsystem. The vte terminals are not related to qemu
>> consoles at all. This simply doesn't belong there and it stands in
>> the way when cleaning up the qemu consoles subsystem. So fix it
>> up, quickly, before it sneaks into a release.
>
>
> My only concern is that if someone had a command line like:
>
> qemu -serial stdio -monitor vc
>
> It now breaks with your series.
Yes. I'm not worried. The switch to gtk is a pretty big one anyway
with a bunch of user interface changes. If we want avoid surprises for
the user at any cost we must not make gtk the default ui.
Also: Once I'm done with the console cleanup it will be easy to make
'vc' actually work with gtk.
> 'vc' is a graphical chardev and it should be up to what UI layer to
> decide how to express it
No.
'vc' is a DisplaySurface filled by the qemu terminal emulation. It's
generic and works with any UI.
'vte' is a chardev data stream linked up to the gtk vte widget.
Obviously works with gtk only.
> What's the issue your having with console cleanup?
It just doesn't fit into the QemuConsoles at all, and with multiple UI's
active (such as gtk+vnc at the same time) it doesn't make sense any more.
cheers,
Gerd
next prev parent reply other threads:[~2013-03-13 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 10:18 [Qemu-devel] [PATCH] chardev: add vte chardev Gerd Hoffmann
2013-03-13 12:29 ` Anthony Liguori
2013-03-13 14:25 ` Gerd Hoffmann [this message]
2013-03-13 15:59 ` Anthony Liguori
2013-03-13 16:33 ` Gerd Hoffmann
2013-03-13 17:27 ` Anthony Liguori
2013-03-14 8:03 ` Gerd Hoffmann
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=51408C70.7010603@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.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).