GNU bug report logs - #64927
30.0.50; kill-ring with no X

Previous Next

Package: emacs;

Reported by: Colin Baxter <m43cap <at> yandex.com>

Date: Sat, 29 Jul 2023 09:48:02 UTC

Severity: normal

Found in version 30.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: m43cap <at> yandex.com, larsi <at> gnus.org, 64927 <at> debbugs.gnu.org
Subject: bug#64927: 30.0.50; kill-ring with no X
Date: Thu, 03 Aug 2023 19:00:18 +0300
> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: m43cap <at> yandex.com,  64927 <at> debbugs.gnu.org,  Lars Ingebrigtsen
>  <larsi <at> 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.




This bug report was last modified 2 years and 21 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.