GNU bug report logs - #78714
30.1; failure binding keys to certain unicode characters

Previous Next

Package: emacs;

Reported by: John Holman <john.g.holman <at> gmail.com>

Date: Sat, 7 Jun 2025 11:48:01 UTC

Severity: normal

Tags: fixed

Found in version 30.1

Fixed in version 30.2

Done: Robert Pluim <rpluim <at> gmail.com>

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: John Holman <john.g.holman <at> gmail.com>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 78714 <at> debbugs.gnu.org
Subject: bug#78714: 30.1; failure binding keys to certain unicode characters
Date: Sat, 07 Jun 2025 15:45:04 +0300
[Please use Reply All" to reply, so as to keep the bug tracker CC'ed.]

> From: John Holman <john.g.holman <at> gmail.com>
> Date: Sat, 7 Jun 2025 13:38:49 +0100
> 
> Many thanks for the fast response. I do think that's a surprising feature and that most users would expect
> "\u00B2" to be interpreted as a unicode character especially given the \u representation, which I think is
> specific to Unicode even if treated as just a variant numerical representation in emacs. Would it make sense
> for emacs to take the \u format into account when interpreting that string?

I don't think this is feasible, since by the time the character is
interpreted the information that it came from a "\uNNN" format is long
gone.  But maybe Stefan (CC'ed) will have some ideas.




This bug report was last modified 4 days ago.

Previous Next


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