From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>,
qemu-devel@nongnu.org, Glauber Costa <glommer@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] new SDL keyboard shortcuts to start and stop VM
Date: Thu, 22 Oct 2009 17:02:29 +0200 [thread overview]
Message-ID: <4AE07405.40403@redhat.com> (raw)
In-Reply-To: <20091022124036.5df991f3@doriath>
Am 22.10.2009 16:40, schrieb Luiz Capitulino:
> On Wed, 21 Oct 2009 19:35:03 +0100
> Jamie Lokier <jamie@shareable.org> wrote:
>> If the monitor accepted ";" as a command separator, to put multiple
>> commands on a single line, <command_list> could just be a quoted
>> string which is processed as a line.
>
> Why is ";" needed?
How else would you specify multiple commands for one macro?
>>
>> - add_key key <key> <command-string>
>> - remove_key <key> <command-string>
>> - list_keys
>
> What's key?
Some kind of key binding. If we allowed all keys, it would probably make
sense to use the sendkeys style format, but I assume we'll only support
ctrl-alt-<letter> which already has a special meaning.
> Ah, it doesn't have macro_del and if we use QObjects we can
> consider saving its json representation in file so that we can
> have macro_load.
You are thinking about having this to avoid typing in the macro each
time you start a VM? For something the user might want to touch I'd
prefer a simple solution like reading ~/.qemurc or something like that
and executing it as a "monitor script".
Kevin
next prev parent reply other threads:[~2009-10-22 15:03 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
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 [this message]
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=4AE07405.40403@redhat.com \
--to=kwolf@redhat.com \
--cc=glommer@gmail.com \
--cc=lcapitulino@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).