From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43830@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#43830: keyboard layout handling incompatible with rest of the OS
Date: Sun, 01 Nov 2020 20:27:41 +0200 [thread overview]
Message-ID: <87v9ep54sy.fsf@mail.linkov.net> (raw)
In-Reply-To: <83y2jlf6wx.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 01 Nov 2020 17:11:58 +0200")
>> What is worse is that in a writable buffer, typing 'й' should insert
>> this character untranslated, but in the same buffer when it's in
>> read-only view mode, typing the same 'й' should translate it to 'q'
>> and quit the buffer with the View-quit command. When using reverse-im
>> with local-function-key-map, the Help buffer says:
>>
>> q (translated from й) runs the command View-quit.
>>
>> So the question is whether it's possible to do the same using
>> XkbTranslateKeyCode? The local-function-key-map is smart enough
>> to not translate self-inserting keys. Can code for XkbTranslateKeyCode
>> use the same condition to detect self-inserting keys?
>
> Why do you want XkbTranslateKeyCode to do this? why not the code in
> keyboard.c that reads the event queue and invokes commands? If we
> make both the key and the character available to keyboard.c, it should
> be able to figure out what is TRT in each situation, I think.
Actually by the phrase "code for XkbTranslateKeyCode" I meant the code
in keyboard.c that could use XkbTranslateKeyCode to do the key translation
between physical keys and characters.
next prev parent reply other threads:[~2020-11-01 18:27 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
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 [this message]
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=87v9ep54sy.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=43830@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.