all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 71479@debbugs.gnu.org
Subject: bug#71479: 30.0.50; describe-key description incorrect when using input methods
Date: Sat, 15 Jun 2024 13:41:14 +0300	[thread overview]
Message-ID: <86bk42v67p.fsf@gnu.org> (raw)
In-Reply-To: <875xughhlb.fsf@gmail.com> (message from Robert Pluim on Mon, 10 Jun 2024 18:45:36 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Date: Mon, 10 Jun 2024 18:45:36 +0200
> 
> 
> emacs -Q
> C-u C-\ cyrillic-translit
> C-h k z h
> 
> =>
>     ж (translated from h ж) runs the command
>     self-insert-command (found in global-map), which is an interactive
>     primitive-function in ‘C source code’.
> 
> This should say '*translated from z h)'. The underlying reason is that
> quail.el messes around with `last-command-event', which confuses
> describe-key.
> 
> I doubt this issue is confined to this particular input method.

Right, it looks like the problem is in this-single-command-raw-keys,
and more deeply in what we store in the raw_keybuf vector.

Stefan, any suggestions for how we could fix this?





  parent reply	other threads:[~2024-06-15 10:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 16:45 bug#71479: 30.0.50; describe-key description incorrect when using input methods Robert Pluim
2024-06-10 22:02 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-11  7:33   ` Robert Pluim
2024-06-11 20:18     ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-15 10:41 ` Eli Zaretskii [this message]
2024-06-15 14:34   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=86bk42v67p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71479@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rpluim@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.