unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Leif Strand <leif@geodynamics.org>
To: Kenichi Handa <handa@m17n.org>
Cc: bug-gnu-emacs@gnu.org, 4924@emacsbugs.donarmstrong.com
Subject: bug#4924: Emacs No Longer Reads Mac Text Files
Date: Mon, 16 Nov 2009 18:13:53 -0800	[thread overview]
Message-ID: <4B0206E1.3010905@geodynamics.org> (raw)
In-Reply-To: <tl7ws1qorz6.fsf@m17n.org>

I added "(setq inhibit-null-byte-detection 1)" to my .emacs, and now 
everything works like a charm.  Thanks!!!

--Leif

Kenichi Handa wrote:
> In article <4B01B0FC.4090505@geodynamics.org>, Leif Strand <leif@geodynamics.org> writes:
> 
>> Glad to hear that CR support is still there.  Indeed, I've played with 
>> it a bit more, and it seems that trivial examples do work.
> 
>> I can't figure out what algorithm Emacs is using to guess the kind of 
>> text file.  So anyway, I've attached a tarball containing two files:
> 
>> * ozymandias.txt:  This a trivial example which does work.  It was 
>> created in BBEdit 4.5.
> 
>> * SqueakV1-18.sources:  This is the file that triggered my complaint. 
>> Emacs 21 correctly identified this as a Mac file.  In Emacs v23.1.50.1, 
>> I see one long line with a bunch of ^M characters.
> 
> Emacs now detects a file that contains NULL bytes as binary
> file and use `no-conversion' for reading that file (see the
> docstring of the variable `inhibit-null-byte-detection').
> And SqueakV1-18.sources cotains NULL bytes at line 26527.
> When I delete that line, the file is correctly detected as
> Mac-eol format.
> 
> ---
> Kenichi Handa
> handa@m17n.org





      reply	other threads:[~2009-11-17  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-14  1:38 bug#4924: Emacs No Longer Reads Mac Text Files Leif Strand
2009-11-16  1:16 ` Kenichi Handa
     [not found]   ` <4B01B0FC.4090505@geodynamics.org>
2009-11-17  1:33     ` Kenichi Handa
2009-11-17  2:13       ` Leif Strand [this message]

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=4B0206E1.3010905@geodynamics.org \
    --to=leif@geodynamics.org \
    --cc=4924@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=handa@m17n.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).