From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: v.schneidermann@gmail.com, 27270@debbugs.gnu.org,
npostavs@users.sourceforge.net
Subject: bug#27270: display-raw-bytes-as-hex generates ambiguous output for Emacs strings
Date: Wed, 27 Apr 2022 14:13:43 +0200 [thread overview]
Message-ID: <87k0bad8qw.fsf@gnus.org> (raw)
In-Reply-To: <b32f2a79-90ed-6f25-a864-95c66033ee0f@cs.ucla.edu> (Paul Eggert's message of "Tue, 26 Apr 2022 09:48:35 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
>> Your last suggestion was to output
>> (format "%cf" 129)
>> => "\x81\x66"
>> I think? Which is changing the data output.
>
> Oh, right. Scratch that. Let's just use "\uXXXX" if multibyte, "\OOO"
> (octal) if unibyte. (This is only when the character precedes a hex
> digit.) That's simpler anyway.
That will also change the output, which display-raw-bytes-as-hex is not
supposed to do.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-27 12:13 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0bad8qw.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=27270@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).