GNU bug report logs - #5050
23.1; efiff: Displaying bytes instead of characters in messages

Previous Next

Full log

Message #51 received at 5050 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: sebastian_rose <at> gmx.de, stephen.berman <at> gmx.net, 5050 <at> debbugs.gnu.org
Subject: Re: bug#5050: 23.1; efiff: Displaying bytes instead of characters
 in messages
Date: Thu, 20 Aug 2020 22:17:02 +0200

[Message part 1 (text/plain, inline)]

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> 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.)

But it's not doing that -- it's loading the files into normal Emacs
buffers, so the normal Emacs autodetecting of coding systems takes
place.

Hm...  to me it looks like it never decodes the output from diff -- it
doesn't care what's on the lines, it just uses the diff codes.

Here's what the output buffer looks like:

[Message part 2 (image/png, inline)]

[Message part 3 (text/plain, inline)]

This is a buffer that the user doesn't see -- instead the real two
buffers are displayed, and the fontising is done there.

But again, I'm not familiar with the code here, but it looks to me that
that's what ediff-extract-diffs is doing.

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.