[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs
From: |
Eli Zaretskii |
Subject: |
bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings |
Date: |
Sat, 02 Sep 2017 16:25:33 +0300 |
unblock 24655 by 27270
thanks
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 11 Jun 2017 10:26:28 -0700
> Cc: v.schneidermann@gmail.com, 27270@debbugs.gnu.org,
> npostavs@users.sourceforge.net
>
> Eli Zaretskii wrote:
> > Then maybe the new hex display should use the \N{U+nnn} format?
>
> If we're going to do that, we might as well use \unnnn, which is shorter. A
> downside of either syntax, though, is the implication that the raw byte is
> intended to be Unicode, which it typically is not. That is partly why I was
> thinking \x{nn} would be better: it'd be clearer to users.
In any case, since this is a "wishlist" bug report, I don't think it
should block the release of Emacs 26.1 (or any other version).
Thanks.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings,
Eli Zaretskii <=