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

Previous Next

Full log

View this message in rfc822 format

From: John Holman <john.g.holman <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 78714 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: bug#78714: 30.1; failure binding keys to certain unicode characters
Date: Sat, 7 Jun 2025 13:46:22 +0100

[Message part 1 (text/plain, inline)]

Thank you.

On Sat, 7 Jun 2025 at 13:45, Eli Zaretskii <eliz <at> gnu.org> wrote:

> [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.
>

[Message part 2 (text/html, inline)]

Previous Next

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