From: Spencer Baugh <sbaugh@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 62626@debbugs.gnu.org
Subject: bug#62626: 29.0.60; describe-key errors on Edit → Paste from Kill Ring → [any item]
Date: Thu, 06 Apr 2023 09:07:46 -0400 [thread overview]
Message-ID: <ier4jpt2m71.fsf@janestreet.com> (raw)
In-Reply-To: <83bkk1qlhi.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Apr 2023 14:49:13 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Sun, 02 Apr 2023 15:06:53 -0400
>>
>> describe-key is also broken with context-menu-mode in a different way,
>> btw. It generates the help buffer fine, but the last key in the
>> sequence is wrong. It looks like read-key-sequence returns a numeric
>> index into the menu for that key, counting up from from the last menu
>> entry and starting at 1, and then the help buffer is interpreting that
>> number as a key.
>
> Please provide a recipe (and perhaps report this as a different bug,
> unless my proposed solution happens to fix this one as well, by sheer
> luck).
>
> Thanks.
Ah I wasn't clear, it's also an issue with yank-menu. Probably
basically the same bug? Recipe:
1. emacs -Q
2. M-x context-menu-mode RET
3. Type "foobar" and kill it
4. C-h k and right click, then "Paste from Kill Menu", then "(any string)".
5. Observe the help buffer claims the key sequence was:
<down-mouse-3> <paste-from-menu> C-a
next prev parent reply other threads:[~2023-04-06 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 18:49 bug#62626: 29.0.60; describe-key errors on Edit → Paste from Kill Ring → [any item] Spencer Baugh
2023-04-02 19:06 ` Spencer Baugh
2023-04-06 11:49 ` Eli Zaretskii
2023-04-06 13:07 ` Spencer Baugh [this message]
2023-04-06 13:49 ` Eli Zaretskii
2023-04-06 11:47 ` Eli Zaretskii
2023-04-06 14:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 12:43 ` Eli Zaretskii
2023-04-08 15:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 17:13 ` Eli Zaretskii
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=ier4jpt2m71.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=62626@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.