[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: |
Thu, 08 Jun 2017 21:59:56 +0300 |
> Cc: npostavs@users.sourceforge.net, 27270@debbugs.gnu.org,
> v.schneidermann@gmail.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 8 Jun 2017 09:24:56 -0700
>
> >> "\x905"
> >>
> >> which is the wrong string visually.
> > How is that different from "\2205" you get under the default settings?
>
> When I cut and paste "\2205" into another Emacs, it evaluates to the
> same two-character string that I started off with because octal escapes
> are limited to 3 octal digits.
That's a different issue. You said "\x905" was wrong visually, so I
asked how is that different, visually, from "\2205".
> When I cut and paste "\x905" I get a
> one-character string because there is no limit to the length of
> hexadecimal escapes. This is a problem, because cut-and-paste should
> continue to copy text accurately even when I'm using terminal windows.
Same thing happens when you copy/paste from an Emacs window which uses
a display table: the pasted string will be different from the original
one. I believe I already pointed that out in this discussion.
> >> "\x80\ 5"
> >>
> >> or via some other means.
> > We do use "some other means": the raw byte has a different face.
>
> That doesn't help when --color=no is specified, or in terminal sessions
> that do not support colors.
In those cases, the octal notation has the same visual problems.
> I prefer monochrome anyway. So this ambiguity will be a real pain
> for me.
I still don't understand how this is different from the octal
notation, but if it is, you can always stay with the default octal
display. That's what I do.
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/06
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/07
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/07
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, npostavs, 2017/06/07
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings,
Eli Zaretskii <=
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/08
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/09
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/09
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/10
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/10
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Eli Zaretskii, 2017/06/11
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, Paul Eggert, 2017/06/11
- bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings, npostavs, 2017/06/10