[Top][All Lists]

[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: Paul Eggert
Subject: bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings
Date: Wed, 7 Jun 2017 17:49:41 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0

On 06/06/2017 10:17 PM, Eli Zaretskii wrote:

What do you mean by "Emacs strings"?

I meant that if I prefer hex to octal for buffer escapes, then when I type this into *scratch*:

  (format "J%cK" ?\u0080) C-j

I almost surely would prefer to see the result displayed as hexadecimal than as "J\200K" (the current behavior). People who prefer hex in one place are quite likely to prefer it in the other.

Here's another suggestion for the buffer problem: separate problematic character pairs by "\ " in the buffer display. That way, my test case would be displayed this way in a buffer;

  x\x90\ 5y

and this will work as expected when cut and pasted into a string, due to the backslash-space syntax already supported for strings. This buffer syntax would be less confusing than the "x\x905y" syntax that is currently used. Under this approach character pair XY is considered to be problematic if X is displayed with a hexadecimal escape and Y is a hexadecimal digit.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]