From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 43632@debbugs.gnu.org
Subject: bug#43632: Raw bytes printed as latin-1 in echo area and *Messages*
Date: Sat, 26 Sep 2020 16:22:10 +0200 [thread overview]
Message-ID: <873634list.fsf@gnus.org> (raw)
In-Reply-To: <83mu1cr5fn.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Sep 2020 17:14:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It is not an anomaly. If you want to see escapes, set
> print-escape-nonascii non-nil.
>
> Also note that what you see is the result of 'eval' printing the
> result, the real result (as returned by prin1) is a unibyte string:
>
> (multibyte-string-p (prin1 "\377")) => nil
>
> (Yes, this is very confusing.)
Could we do something about this confusion?
This came up because I just couldn't make sense of what I was seeing
when trying to work with raw bytes -- it seemed to be that Emacs was
auto-promoting unibyte strings (with bytes >127) to multibyte strings...
until I started calling multibyte-string-p on everything instead.
I'm guessing I'm not the only person confused by this stuff.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-26 14:22 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873634list.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 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.