qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM
Date: Wed, 21 Oct 2009 11:52:32 -0200	[thread overview]
Message-ID: <5d6222a80910210652q3b005ca6ub950a2014bfbaa41@mail.gmail.com> (raw)
In-Reply-To: <4ADEB7EF.3060800@redhat.com>

On Wed, Oct 21, 2009 at 5:27 AM, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 20.10.2009 19:08, schrieb Daniel P. Berrange:
>> On Tue, Oct 20, 2009 at 12:40:08PM +0200, Kevin Wolf wrote:
>>> Am 20.10.2009 00:20, schrieb Anthony Liguori:
>>>> Mulyadi Santosa wrote:
>>>>> IMO, it would be faster if we provide keyboard shortcuts that will
>>>>> stop and resume VM execution right from SDL guest interface, rather
>>>>> than switching to console monitor first and type "s" or "c"
>>>>> respectively.
>>>>>
>>>>
>>>> Is this really common of an operation that you would need an escape key
>>>> for it?
>>>>
>>>> Why are you so frequently stopping and continuing a guest?
>>>
>>> Why are you all trying to explain to him that actually he doesn't want
>>> to have this feature? I could have used it, too, at times (stop the
>>> guest to have enough time to attach gdb, for example). There are other
>>> ways to do it (although they are not as simple) and I used them, but
>>> that doesn't make this feature less useful.
>>>
>>> Does it take anything away for you? Or do you have plans to use those
>>> keys otherwise? If not, why not add a feature that some might find
>>> useful, even though others don't?
>>
>> The problem with adding lots of magic key-sequences, is that the more
>> you add, the more likely they are to clash with something that the
>> guest OS wants to use. You may make this use case work, but break
>> someone else's use case. Thus, IMHO, magic key sequences should be kept
>> to the bare minimum neccessary to access functionality for which there
>> is no other viable access method.
>
> Ok, you have a point there. But why do we have key sequences for
> fullscreen and resizing the SDL window back to its original size then?
> Both are things that could be accessed through monitor commands as well.
> And you don't need the right timing for resizing the window - unlike
> stopping the VM. So I would be really happy with swapping those for a
> "stop VM" shortcut.

Why don't we provide a mechanism to make a macro out of a sequence of
monitor commands, and let the user assign whatever he wants out of that?


-- 
Glauber  Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

  reply	other threads:[~2009-10-21 13:52 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 16:24 [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM Mulyadi Santosa
2009-10-19 22:20 ` Anthony Liguori
2009-10-20  3:16   ` Mulyadi Santosa
2009-10-20  7:58     ` Gerd Hoffmann
2009-10-20  8:12     ` Daniel P. Berrange
2009-10-20 10:40   ` Kevin Wolf
2009-10-20 16:59     ` Anthony Liguori
2009-10-20 17:08     ` Daniel P. Berrange
2009-10-20 22:14       ` Mulyadi Santosa
2009-10-21  7:27       ` Kevin Wolf
2009-10-21 13:52         ` Glauber Costa [this message]
2009-10-21 16:04           ` Mulyadi Santosa
2009-10-21 16:24             ` Glauber Costa
2009-10-21 16:44               ` Mulyadi Santosa
2009-10-21 16:48                 ` Glauber Costa
2009-10-21 18:35                 ` Jamie Lokier
2009-10-22 14:40                   ` Luiz Capitulino
2009-10-22 15:02                     ` Kevin Wolf
2009-10-22 16:32                       ` Luiz Capitulino
2009-10-22 15:40                     ` Anthony Liguori
2009-10-22 16:38                       ` Luiz Capitulino
2009-10-22 18:32                         ` Anthony Liguori
     [not found]                           ` <m33a5bj851.fsf@neno.mitica>
2009-10-23  7:40                             ` [Qemu-devel] " Kevin Wolf
2009-10-23 11:23                               ` Mulyadi Santosa
2009-10-23 11:45                                 ` Kevin Wolf
2009-10-23 13:59                                   ` Anthony Liguori
2009-10-23 14:36                                     ` Kevin Wolf
2009-10-25 15:28                                     ` Avi Kivity
2009-10-25 15:44                                       ` Luiz Capitulino
2009-10-26 13:45                                       ` Anthony Liguori
2009-10-26 14:13                                         ` Avi Kivity
2009-10-26 15:04                                           ` Anthony Liguori
2009-10-26 15:07                                             ` Avi Kivity
2009-10-26 15:49                                               ` Anthony Liguori
2009-10-26 16:08                                                 ` Avi Kivity
2009-10-26 16:17                                                   ` Anthony Liguori
2009-10-27  9:11                                                   ` Gerd Hoffmann
2009-10-27  9:28                                                     ` Avi Kivity
2009-10-21 16:55           ` [Qemu-devel] " Anthony Liguori
2009-10-21 17:01             ` Mulyadi Santosa
2009-10-21 17:04             ` Glauber Costa
2009-10-21 18:08               ` Anthony Liguori
2009-10-22  7:58                 ` Kevin Wolf

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=5d6222a80910210652q3b005ca6ub950a2014bfbaa41@mail.gmail.com \
    --to=glommer@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=mulyadi.santosa@gmail.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).