unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mattiase@acm.org, 43632@debbugs.gnu.org
Subject: bug#43632: Raw bytes printed as latin-1 in echo area and *Messages*
Date: Sun, 27 Sep 2020 13:13:31 +0200	[thread overview]
Message-ID: <87blhr79r8.fsf@gnus.org> (raw)
In-Reply-To: <83k0wfo4y2.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 27 Sep 2020 14:05:25 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> In the *scratch* buffer, C-x C-e:
>> 
>> "\377"
>> => "\377"
>> 
>> But the echo area says "\xff".
>> 
>> because I have (setq display-raw-bytes-as-hex t).
>
> So you've explicitly asked for that, no?

I have, so I guess the only confusing thing is that it's still "\377" in
the scratch buffer?

>> (string-to-multibyte "\377")
>> => "\377"
>> 
>> And the echo area says "\377", as expected.
>
> That's unrelated: Emacs behaved the same before my changes.

Yup.  But don't we call these "raw bytes", too?  I was just idly wondering
whether the display of these should also be affected by
`display-raw-bytes-as-hex'...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-09-27 11:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26 12:51 bug#43632: Raw bytes printed as latin-1 in echo area and *Messages* Mattias Engdegård
2020-09-26 14:05 ` Andreas Schwab
2020-09-26 14:14 ` Eli Zaretskii
2020-09-26 14:22   ` Lars Ingebrigtsen
2020-09-26 14:26     ` Eli Zaretskii
2020-09-26 16:00   ` Mattias Engdegård
2020-09-26 16:10     ` Eli Zaretskii
2020-09-26 16:53       ` Mattias Engdegård
2020-09-26 16:57         ` Eli Zaretskii
2020-09-26 17:27           ` Eli Zaretskii
2020-09-27 10:58             ` Lars Ingebrigtsen
2020-09-27 11:05               ` Eli Zaretskii
2020-09-27 11:13                 ` Lars Ingebrigtsen [this message]
2020-09-27 11:25                   ` Eli Zaretskii
2020-09-27 11:36                     ` Lars Ingebrigtsen
2020-09-27 11:43                       ` Eli Zaretskii
2020-09-26 19:53           ` Mattias Engdegård
2020-09-27  5:56             ` Eli Zaretskii

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=87blhr79r8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=43632@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mattiase@acm.org \
    /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).