GNU bug report logs - #17714
24.4.50; File coding system not detected correctly

Previous Next

Full log

Message #13 received at 17714-done <at> debbugs.gnu.org (full text, mbox):

From: Jorgen Schaefer <forcer <at> forcix.cx>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 17714-done <at> debbugs.gnu.org
Subject: Re: bug#17714: 24.4.50; File coding system not detected correctly
Date: Fri, 6 Jun 2014 11:51:57 +0200

On Fri, 06 Jun 2014 12:22:15 +0300
Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Jorgen Schaefer <forcer <at> forcix.cx>
> > Date: Fri, 06 Jun 2014 10:24:53 +0200
> > 
> > Since a few days ago, current trunk stopped detecting file coding
> > systems correctly for me. For a file that is opened as utf-8 with
> > stable Emacs, it now says (using emacs -q, fundamental-mode):
> > 
> > -----
> > buffer-file-coding-system is a variable defined in `C source code'.
> > Its value is no-conversion
> > Local in buffer Todo; global value is utf-8-unix
> > -----
> > 
> > M-x revert-buffer-with-coding-system RET utf-8 RET works fine.
> 
> Please send an example file where you see this problem.

Hm. I *thought* I had seen the problem with more than one file, but it
turns out it was only one. The problem was that the file contained ^@
(zero bytes) from a yank from some process output. Which of course is
not valid utf-8.

Now I wonder why the file saved without error. There was some weird
vc error as well. Can't reproduce this now, though. So meh.

Sorry for the noise, nothing to see here. :-)

Jorgen

Previous Next

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