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: Thu, 14 Mar 2013 09:03:58 +0100 [thread overview]
Message-ID: <5141846E.1040000@redhat.com> (raw)
In-Reply-To: <87r4jjrz0x.fsf@codemonkey.ws>
Hi,
>> Well, it already is. Not that I want extend it or would recommend using
>> it if there are better options. But there is no reason to break it, and
>> it is useful to me now and then.
>
> qemu -display sdl -vnc :1 -serial vc
>
> Continues to do what it did before.
Yes.
> qemu -display gtk -vnc :1 -serial vc
>
> Seg faults which is bad. I can look more deeply into that.
The "console: data structures overhaul" patch series posted earlier this
week fixes this.
> But with your proposal, the above would either (1) use the old style
> console in GTK or (2) not make the console available in gtk.
Yes. If you want the text consoles on vnc you must use 'vc'. We then
can decide to show or not show the 'vc' consoles with gtk too, at the
end this will be just two lines of code.
If you don't care about text consoles on vnc you can pic 'vte'. Then
they will show up on gtk only.
And having separate chardevs for 'vc' and 'vte' empowers the user to
pick what he wants.
> Both are bad because they have consequences for:
>
> qemu -serial vc
>
> The above must continue to have a reasonable behavior by default and
> with GTK as the default, that means using VTE as the terminal emulation.
Why? We can wind up vc text consoles for gtk, then the above will give
you a text console. As compatible as possible, as it will be the
exactly same thing you got in qemu 1.4 with sdl as default ui.
If you want the new features, use the new options. That always has been
the policy with qemu, I fail to see why gtk should be different here.
> If you can find a way to make 'qemu -display gtk -vnc :1 -serial vc'
> behave without impacting the other use-cases, I'm open to that but just
> renaming 'vc' to 'vte' for gtk is going to be a compat breaker.
IMO current gtk code breaks compat by hijacking 'vc'.
cheers,
Gerd
prev parent reply other threads:[~2013-03-14 8:04 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
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 [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=5141846E.1040000@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).