From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43632@debbugs.gnu.org
Subject: bug#43632: Raw bytes printed as latin-1 in echo area and *Messages*
Date: Sat, 26 Sep 2020 18:53:39 +0200 [thread overview]
Message-ID: <8E496ABD-F07C-4BBD-ABC5-8BC4FFC0A9F8@acm.org> (raw)
In-Reply-To: <838scwr02l.fsf@gnu.org>
26 sep. 2020 kl. 18.10 skrev Eli Zaretskii <eliz@gnu.org>:
> We were talking about M-:.
Sorry, typo of mine. Thanks for the correction.
> And that does call prin1. And prin1 does
> produce a unibyte string, the reason for the display that confused you
> is elsewhere.
We probably disagree about the details here, but let's leave prin1 aside; it doesn't need to be changed in order to improve the M-: user experience.
What about this little tweak?
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -1797,6 +1797,7 @@ eval-expression
(let ((print-length (unless no-truncate eval-expression-print-length))
(print-level (unless no-truncate eval-expression-print-level))
(eval-expression-print-maximum-character char-print-limit)
+ (print-escape-nonascii t)
(deactivate-mark))
(let ((out (if insert-value (current-buffer) t)))
(prog1
That way, it works more like the other interactive Lisp evaluation commands in this particular respect.
Do you think a NEWS entry is called for?
next prev parent reply other threads:[~2020-09-26 16:53 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 [this message]
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
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=8E496ABD-F07C-4BBD-ABC5-8BC4FFC0A9F8@acm.org \
--to=mattiase@acm.org \
--cc=43632@debbugs.gnu.org \
--cc=eliz@gnu.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).