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

Previous Next

Package: emacs;

Reported by: Sebastian Rose <sebastian_rose <at> gmx.de>

Date: Thu, 26 Nov 2009 19:20:03 UTC

Severity: minor

Tags: fixed

Fixed in version 28.1

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

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.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 23:12:52 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: sebastian_rose <at> gmx.de,  stephen.berman <at> gmx.net,  5050 <at> debbugs.gnu.org
> Date: Thu, 20 Aug 2020 22:01:57 +0200
> 
> Eli Zaretskii <eliz <at> 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...

Wait, the problematic text appears in the Ediff error buffer, right?
So we should perhaps simply decode it?  Does evaluating the below in
that buffer fixes the problem?

  M-: (decode-coding-region (point-min) (point-max) 'undecided) RET




This bug report was last modified 4 years and 278 days ago.

Previous Next


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