From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: 43830@debbugs.gnu.org, juri@linkov.net
Subject: bug#43830: keyboard layout handling incompatible with rest of the OS
Date: Wed, 28 Oct 2020 17:06:04 +0200 [thread overview]
Message-ID: <83y2jqcrvn.fsf@gnu.org> (raw)
In-Reply-To: <CAG7BpaoPi96irUWr4SPvNLKmTeknxpOEZiX4wzMge8=L8uEKQQ@mail.gmail.com> (message from Paul Pogonyshev on Wed, 28 Oct 2020 01:43:04 +0100)
> From: Paul Pogonyshev <pogonyshev@gmail.com>
> Date: Wed, 28 Oct 2020 01:43:04 +0100
> Cc: Juri Linkov <juri@linkov.net>, 43830@debbugs.gnu.org
>
> Apparently what Java does internally is calling function
> XkbTranslateKeyCode() to translate 'keycode' that corresponds
> to a physical key into a character using the current XKB layout.
Is XKB universally available? AFAICT, we don't require it, but use it
if available (not for XkbTranslateKeyCode, though).
> However, in Elisp this is further complicated by there being no
> real KeyEvent structure, instead it's a single integer as far as I
> can see.
Why would you need that? If we decide to use XkbTranslateKeyCode, we
could translate the keycode in C, according to some logic that took
into account the modifiers and perhaps also some user options, and
returned the resulting translated character.
next prev parent reply other threads:[~2020-10-28 15:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 15:34 bug#43830: keyboard layout handling incompatible with rest of the OS Paul Pogonyshev
2020-10-06 17:26 ` Eli Zaretskii
2020-10-06 17:48 ` Paul Pogonyshev
2020-10-06 18:00 ` Eli Zaretskii
2020-10-06 18:46 ` Juri Linkov
2020-10-06 18:59 ` Paul Pogonyshev
2020-10-06 20:34 ` Juri Linkov
2020-10-06 21:05 ` Paul Pogonyshev
2020-10-07 8:16 ` Juri Linkov
2020-10-07 8:51 ` Eli Zaretskii
2020-10-07 19:01 ` Juri Linkov
2020-10-08 8:50 ` Eli Zaretskii
2020-10-08 13:58 ` Paul Pogonyshev
2020-10-28 0:43 ` Paul Pogonyshev
2020-10-28 15:06 ` Eli Zaretskii [this message]
2020-10-28 16:16 ` Paul Pogonyshev
2020-10-28 16:31 ` Eli Zaretskii
2020-11-01 0:19 ` Paul Pogonyshev
2020-11-01 15:09 ` Eli Zaretskii
2020-11-01 7:53 ` Juri Linkov
2020-11-01 15:11 ` Eli Zaretskii
2020-11-01 18:27 ` Juri Linkov
2020-11-01 18:49 ` Eli Zaretskii
2020-11-01 16:51 ` Paul Pogonyshev
2020-11-01 17:24 ` Eli Zaretskii
2020-11-01 18:56 ` Paul Pogonyshev
2020-11-01 19:32 ` Eli Zaretskii
2020-11-01 20:06 ` Paul Pogonyshev
2020-11-02 4:41 ` Arthur Miller
2020-11-02 15:38 ` Eli Zaretskii
2020-11-01 7:48 ` Juri Linkov
2020-10-07 10:37 ` Paul Pogonyshev
2020-10-07 19:04 ` Juri Linkov
2020-10-07 20:08 ` Paul Pogonyshev
2020-10-07 20:25 ` Juri Linkov
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=83y2jqcrvn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43830@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=pogonyshev@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.