unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jorgen Schaefer <forcer@forcix.cx>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17714-done@debbugs.gnu.org
Subject: bug#17714: 24.4.50; File coding system not detected correctly
Date: Fri, 6 Jun 2014 11:51:57 +0200	[thread overview]
Message-ID: <20140606115157.6b79f180@forcix.jorgenschaefer.de> (raw)
In-Reply-To: <83bnu64cl4.fsf@gnu.org>

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

> > From: Jorgen Schaefer <forcer@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





  reply	other threads:[~2014-06-06  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  8:24 bug#17714: 24.4.50; File coding system not detected correctly Jorgen Schaefer
2014-06-06  9:22 ` Eli Zaretskii
2014-06-06  9:51   ` Jorgen Schaefer [this message]
2014-06-06 11:44     ` 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=20140606115157.6b79f180@forcix.jorgenschaefer.de \
    --to=forcer@forcix.cx \
    --cc=17714-done@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 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).