all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 21:53:01 +0200	[thread overview]
Message-ID: <44F138D7-6677-426A-829C-3E40F8F06767@acm.org> (raw)
In-Reply-To: <83wo0gpjbj.fsf@gnu.org>

26 sep. 2020 kl. 18.57 skrev Eli Zaretskii <eliz@gnu.org>:

> We are going to disregard user preferences regarding escapes?

If you mean print-escape-nonascii then it has no effect on values printed from interactive Lisp evaluation in the *scratch* buffer (C-j) either. Since that behaviour is less deceptive and appears more useful in general, it would both bring some consistency to the mess and make users happier. It not only fixes M-: but also C-x C-e and C-M-x.

> I'd rather risk something like the below instead:

By all means -- almost as good and better then what we have today.






  parent reply	other threads:[~2020-09-26 19: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
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 [this message]
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=44F138D7-6677-426A-829C-3E40F8F06767@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 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.