From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sebastian_rose@gmx.de, stephen.berman@gmx.net, 5050@debbugs.gnu.org
Subject: bug#5050: 23.1; efiff: Displaying bytes instead of characters in messages
Date: Thu, 20 Aug 2020 22:01:57 +0200 [thread overview]
Message-ID: <87wo1tjdca.fsf@gnus.org> (raw)
In-Reply-To: <83tuwxayh3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Aug 2020 22:50:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> And anyway, Stephen just answered my question, and the diffs are
> displayed correctly with non-ASCII characters, not as raw bytes. So
> there's more here than meets the eye.
They are, but the output in that buffer is just raw bytes -- no matter
whether the output is from stderr or stdout. There must be a decoding
thing that takes place later, but I'm still looking for where that
happens. (I'm wholly unfamiliar with the ediff code.)
When I've found that, the fix would be to apply whatever it's doing to
the error buffer, too...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-20 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 20:13 bug#5050: 23.1; efiff: Displaying bytes instead of characters in messages Sebastian Rose
2009-11-27 16:01 ` Kevin Rodgers
2020-08-20 18:38 ` Lars Ingebrigtsen
2020-08-20 18:53 ` Stephen Berman
2020-08-20 19:21 ` Eli Zaretskii
2020-08-20 19:35 ` Stephen Berman
2020-08-20 19:42 ` Eli Zaretskii
2020-08-20 19:28 ` Lars Ingebrigtsen
2020-08-20 19:42 ` Lars Ingebrigtsen
2020-08-20 19:50 ` Eli Zaretskii
2020-08-20 20:01 ` Lars Ingebrigtsen [this message]
2020-08-20 20:12 ` Eli Zaretskii
2020-08-20 20:18 ` Lars Ingebrigtsen
2020-08-20 20:24 ` Lars Ingebrigtsen
2020-08-20 20:36 ` Stephen Berman
2020-08-21 11:21 ` Lars Ingebrigtsen
2020-08-20 20:17 ` Lars Ingebrigtsen
2020-08-20 19:51 ` Stephen Berman
2020-08-20 20:14 ` 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=87wo1tjdca.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=5050@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sebastian_rose@gmx.de \
--cc=stephen.berman@gmx.net \
/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).