all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Spencer Baugh <sbaugh@janestreet.com>, 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 10:07:47 -0400	[thread overview]
Message-ID: <jwvmt3lku6s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83cz4hqljl.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Apr 2023 14:47:58 +0300")

> An alternative solution for the original problem would be to teach
> event-basic-type and event-modifiers about "events" that happen to be
> strings.

Since `read-key-sequence` returns those, we should probably teach
`event-*` functions to deal with them.

But since they don't agree with `eventp`, maybe we should also consider
deprecating such "weird keys".

FWIW, that very same "Paste from Kill Menu" is constructed differently in
`context-menu-region` where it doesn't suffer from this problem (it
uses integers instead of strings, as keys).


        Stefan






  reply	other threads:[~2023-04-06 14: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
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 [this message]
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=jwvmt3lku6s.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62626@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=sbaugh@janestreet.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.