all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
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:49:03 +0200	[thread overview]
Message-ID: <83361sgbfk.fsf@gnu.org> (raw)
In-Reply-To: <87v9ep54sy.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 01 Nov 2020 20:27:41 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: pogonyshev@gmail.com,  43830@debbugs.gnu.org
> Date: Sun, 01 Nov 2020 20:27:41 +0200
> 
> > 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.

If we keep both the translated and the untranslated character in the
queue, we won't need to call XkbTranslateKeyCode from keyboard.c,
because we'd already have the information.





  reply	other threads:[~2020-11-01 18:49 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
2020-11-01 18:49                               ` Eli Zaretskii [this message]
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=83361sgbfk.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.