Re: problem with system_eol_type

[Stefan Monnier <monnier@iro.umontreal.ca>]

>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Mon, Jul 31 2006, Kenichi Handa wrote:
>> I've got several complaints about the change I made a few
>> months ago regarding the handling of the default eol-type.
>> 
>> Previously, when a coding system without explicit eol-type
>> (e.g. iso-latin-1) was specified for encoding, Unix-like
>> eol-type is selected on any platform.
>> 
>> The change I made was to use an eol-type set to
>> system_eol_type (CRLF on Windows, LF otherwise) in such a
>> case.  To me, that change was just a bug fix.
>> 
>> But, the bug-reports say that there are many codes that
>> assumes the previous behaviour, and some of them now don't
>> work well on Windows.

I'd argue that those pieces of code had bugs: if your code depends on a Unix
style EOL, it should say so explicitly.

> FWIW, two examples in Gnus where that doubled newlines appeared in
> mail messages and NOV (overview) files weren't read/written correctly
> anymore, see this discussion on the Gnus list:
> <http://thread.gmane.org/gmane.emacs.gnus.general/63496/focus=63502>

Is there any good reason why Gnus uses coding systems of the form `foo'
rather than `foo-unix'?

This said, there's clearly a problem of backward compatibility since the
"buggy" code worked in Emacs-21.


        Stefan