From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: m43cap@yandex.com, larsi@gnus.org, 64927@debbugs.gnu.org
Subject: bug#64927: 30.0.50; kill-ring with no X
Date: Thu, 03 Aug 2023 19:00:18 +0300 [thread overview]
Message-ID: <83y1isw1yl.fsf@gnu.org> (raw)
In-Reply-To: <jwvh6pg89p4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 03 Aug 2023 11:11:24 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: m43cap@yandex.com, 64927@debbugs.gnu.org, Lars Ingebrigtsen
> <larsi@gnus.org>
> Date: Thu, 03 Aug 2023 11:11:24 -0400
>
> The ["create a file"] above is an "internal" key-sequence of length
> 1 that happens to use a string as the sole key.
>
> `possibly_translate_key_sequence` instead is trying to handle the new
> "external" key-sequence format [<KBDSTRING>] where <KBDSTRING> is using
> the `kbd` syntax, i.e. the string is not itself a key but represents
> a key-sequence.
>
> IOW, this is a fundamental incompatibility introduced by the support for
> this new [<KBDSTRING>] format in `define-key`: keys cannot be arbitrary
> objects any more (among other things they can't be strings any more).
Hmm... that's bad, isn't it? Menus always supported strings like
that, so we have no lost that? Do you see any reasonably practical
way to get that back?
And here we are not calling define-key, we are calling lookup-key
instead, btw.
next prev parent reply other threads:[~2023-08-03 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 9:47 bug#64927: 30.0.50; kill-ring with no X Colin Baxter
2023-07-29 11:25 ` Colin Baxter
2023-08-03 9:51 ` Eli Zaretskii
2023-08-03 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 16:00 ` Eli Zaretskii [this message]
2023-08-03 16:06 ` Eli Zaretskii
2023-08-03 16:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-03 18:26 ` Eli Zaretskii
2023-08-03 21:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-04 6:14 ` Colin Baxter
2023-08-04 6:38 ` Eli Zaretskii
2023-08-03 19:55 ` Colin Baxter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1isw1yl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64927@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=m43cap@yandex.com \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).