bug#4924: Emacs No Longer Reads Mac Text Files

bug#4924: Emacs No Longer Reads Mac Text Files

[Leif Strand]

Dear Emacs maintainers,

Why is it that my new version of Emacs (v23.1.50.1) no longer 
understands Mac-format (CR) text files?  It still reads DOS (CRLF) files 
just fine.  Why remove support for one but not the other?

It is impossible to imagine that Mac format text files were a 
maintenance burden.  What is the point of gleefully deleting working 
code that was causing zero problems?

I see an upgrade to Emacs v21 in my future.

--Leif Strand

bug#4924: Emacs No Longer Reads Mac Text Files

[Kenichi Handa]

In article <4AFE0A0E.4050709@geodynamics.org>, Leif Strand <leif@geodynamics.org> writes:

> Why is it that my new version of Emacs (v23.1.50.1) no longer 
> understands Mac-format (CR) text files?  It still reads DOS (CRLF) files 
> just fine.  Why remove support for one but not the other?

We didn't remove that support at least by intention.  I
can't reproduce that kind of bug.  Please give us an example
file of Mac-format that can't be recognized as Mac-format.

---
Kenichi Handa
handa@m17n.org

bug#4924: Emacs No Longer Reads Mac Text Files

[Kenichi Handa]

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

bug#4924: Emacs No Longer Reads Mac Text Files

[Leif Strand]

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