From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 0/5] keymap: support kbd layouts with multiple mappings for the same key.
Date: Fri, 16 Feb 2018 15:44:13 +0100 [thread overview]
Message-ID: <20180216144418.21986-1-kraxel@redhat.com> (raw)
The reverse keymap (-k $map) code has problems dealing with keymaps
where multiple key combinations can create the same keysym, because
it can store a single keycode per keysym only. This series fixes it
and does some cleanups along the way.
Gerd Hoffmann (5):
keymap: make struct kbd_layout_t private to ui/keymaps.c
keymap: use glib hash for kbd_layout_t
keymap: numpad keysyms and keycodes are fixed
keymap: record multiple keysym -> keycode mappings
keymap: consider modifier state when picking a mapping
ui/keymaps.h | 29 ++--------
ui/curses.c | 3 +-
ui/keymaps.c | 167 +++++++++++++++++++++++++++++---------------------------
ui/sdl.c | 6 +-
ui/vnc.c | 9 ++-
ui/trace-events | 2 +-
6 files changed, 108 insertions(+), 108 deletions(-)
--
2.9.3
next reply other threads:[~2018-02-16 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 14:44 Gerd Hoffmann [this message]
2018-02-16 14:44 ` [Qemu-devel] [PATCH 1/5] keymap: make struct kbd_layout_t private to ui/keymaps.c Gerd Hoffmann
2018-02-16 14:44 ` [Qemu-devel] [PATCH 2/5] keymap: use glib hash for kbd_layout_t Gerd Hoffmann
2018-02-16 14:44 ` [Qemu-devel] [PATCH 3/5] keymap: numpad keysyms and keycodes are fixed Gerd Hoffmann
2018-02-16 14:44 ` [Qemu-devel] [PATCH 4/5] keymap: record multiple keysym -> keycode mappings Gerd Hoffmann
2018-02-16 14:44 ` [Qemu-devel] [PATCH 5/5] keymap: consider modifier state when picking a mapping 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=20180216144418.21986-1-kraxel@redhat.com \
--to=kraxel@redhat.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).