From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu (linux) and keymaps
Date: Tue, 30 May 2006 18:45:57 -0400 [thread overview]
Message-ID: <20060530224557.GA19572@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <200605301637.50351.harrisonmetz@gmail.com>
On Tue, May 30, 2006 at 04:37:50PM -0500, Harrison Metzger wrote:
> My bug is when I try to toggle fullscreen with the ctrl+alt+f shortcut nothing
> happens. So I tried ctrl+alt+u (because on dvorak u is where the f is) and it
> worked. So it appears as if qemu is using raw scancodes instead or keys.
Yes, qemu uses X keycodes instead of X keysyms.
> I
> looked at the man page (after googling a bit) and it says I should not have
> to use the language (-k) option since I have PC linux. But even if I did
> there is no dvorak keymap available.
This isn't entirely true - some users of PC linux will need to use a keymap
file.
Generally this is whenever you need to redefine the meaning of a keycode (as
the dvorak keyboard layout does).
> This bug is minor because it took 15
> seconds to figure out to hit ctrl+alt+u and because there are not that many
> users of the dvorak keyboard. But it would be nice to have a dvorak keymap
> just for the sake of completion on your wonderful project.
Should be easy enough for someone (such as yourself) to make one.
qemu's keymap layout is quite simple and you can figure out the mapping
between keys and keycodes via xev or xmodmap.
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2006-05-30 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 21:37 [Qemu-devel] Qemu (linux) and keymaps Harrison Metzger
2006-05-30 22:45 ` Jim C. Brown [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=20060530224557.GA19572@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).