From: Paul Eggert <eggert@cs.ucla.edu>
To: Vasilij Schneidermann <v.schneidermann@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
27270@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings
Date: Sun, 24 Apr 2022 15:46:55 -0700 [thread overview]
Message-ID: <038f65e7-2030-eb3d-cd3a-678a325b0ddb@cs.ucla.edu> (raw)
In-Reply-To: <CAPGgwWRbGyBTzFQxy1MY_+BfjupPH+ox1B76AuTLBvrVTupBBQ@mail.gmail.com>
On 4/24/22 02:56, Vasilij Schneidermann wrote:
> Under which conditions exactly does the bug happen?
I run into it with emacs -nw or equivalent, which I often use when I
have a high-latency network connection so GUI Emacs is too slow. A few
people even run Emacs from text consoles, with no graphics or windowing
system at all, though I'm usually not that hard-core.
> trying to work around terminals being bad doesn't
> seem worth the extra effort.
Please bear with us poor users who don't always use GUIs...
> what exactly should the logic be here?
> Detect if there's a preceding hex escaped byte and if yes, display
> adjacent bytes that are formatted using hex characters using escaping,
> too?
Simpler than that. When hex-escaping a character, Emacs would look at
the next character and if it's hexadecimal would print "\ " (or some
similar escaping approach). This is a simple test and won't hurt
printing performance much in the usual case.
next prev parent reply other threads:[~2022-04-24 22:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 3:57 bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings Paul Eggert
2017-06-07 5:17 ` Eli Zaretskii
2017-06-08 0:49 ` Paul Eggert
2017-06-08 1:07 ` npostavs
2017-06-08 15:20 ` Eli Zaretskii
2017-06-08 15:56 ` Paul Eggert
2017-06-08 16:11 ` Eli Zaretskii
2017-06-08 16:24 ` Paul Eggert
2017-06-08 18:59 ` Eli Zaretskii
2017-06-08 19:43 ` Paul Eggert
2017-06-08 19:56 ` Eli Zaretskii
2017-06-08 20:35 ` Paul Eggert
2017-06-09 6:00 ` Eli Zaretskii
2017-06-09 23:44 ` Paul Eggert
2017-06-10 7:24 ` Eli Zaretskii
2017-06-11 0:04 ` Paul Eggert
2017-06-11 14:48 ` Eli Zaretskii
2017-06-11 17:26 ` Paul Eggert
2017-09-02 13:25 ` Eli Zaretskii
2022-04-23 14:00 ` Lars Ingebrigtsen
2022-04-24 7:10 ` Paul Eggert
2022-04-24 9:56 ` Vasilij Schneidermann
2022-04-24 10:26 ` Andreas Schwab
2022-04-24 10:51 ` Vasilij Schneidermann
2022-04-24 11:01 ` Andreas Schwab
2022-04-24 11:29 ` Lars Ingebrigtsen
2022-04-24 22:46 ` Paul Eggert [this message]
2022-04-24 11:24 ` Lars Ingebrigtsen
2022-04-24 22:35 ` Paul Eggert
2022-04-25 7:40 ` Lars Ingebrigtsen
2022-04-25 16:49 ` Paul Eggert
2022-04-26 10:06 ` Lars Ingebrigtsen
2022-04-26 16:48 ` Paul Eggert
2022-04-27 12:13 ` Lars Ingebrigtsen
2022-04-27 17:21 ` Paul Eggert
2022-04-27 17:22 ` Lars Ingebrigtsen
2022-04-28 17:58 ` Paul Eggert
2017-06-10 22:52 ` npostavs
2017-06-11 0:10 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=038f65e7-2030-eb3d-cd3a-678a325b0ddb@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=27270@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@users.sourceforge.net \
--cc=v.schneidermann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.