From: Gerd Hoffmann <kraxel@redhat.com>
To: Ryan El Kochta <relkochta@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] input-linux: customizable grab toggle keys v4
Date: Tue, 22 Jan 2019 10:54:04 +0100 [thread overview]
Message-ID: <20190122095404.nskppqj6doo3yquo@sirius.home.kraxel.org> (raw)
In-Reply-To: <20190120041427.21602-1-relkochta@gmail.com>
On Sat, Jan 19, 2019 at 11:14:27PM -0500, Ryan El Kochta wrote:
> This patch adds a new option to the input-linux object:
>
> grab-toggle=[key-combo]
>
> The key combination can be one of the following:
>
> * ctrl-ctrl
left ctrl + right ctrl.
> * alt-alt
Same.
> * meta-meta
Same.
> * ctrl-alt
This is actually left ctrl + left alt (not any ctrl / alt) in the code.
Ctrl+Alt+Key isn't that uncommon as hotkey, linux console switching uses
Ctrl+Alt+Fn for example. Also some GUI apps use Ctrl+Alt+Someletter for
less frequently used functions when they run out of Ctrl+Someletter
hotkeys. I'd suggest to drop this one.
> * scrolllock
> * ctrl-scrolllock
This likewise is actually left ctrl + scrolllock in the code.
> * ctrl-backtick
Not a good idea. backtick has no fixed location, depends on the
keyboard layout.
So, the naming is a bit tricky here. If only the left ctrl key actually
works we should say so in the name and call it "lctrl-scrolllock". Or
leave the name and allow both ctrl keys.
For the ctrl-ctrl (and simliar) hotkeys I think it doesn't matter much
whenever we call them "ctrl-ctrl" or "lctrl-rctrl". It is kida obvious
that you need both the left and right one when you should press two
control keys. But I think it should be consistent with what we pick for
ctrl-scrolllock.
I think sticking with the current names and make both ctrl keys work
with scrolllock is the better way.
cheers,
Gerd
prev parent reply other threads:[~2019-01-22 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 4:14 [Qemu-devel] [PATCH] input-linux: customizable grab toggle keys v4 Ryan El Kochta
2019-01-22 9:54 ` 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=20190122095404.nskppqj6doo3yquo@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=relkochta@gmail.com \
/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).