Re: Double Newlines

[Katsumi Yamaoka <yamaoka@jpl.org>]

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Hi,

I don't know whether it is related to David Abrahams' problem,
but I heard that the most recent Emacs 22 built on Windows
behaves unlike the old ones.

When saving a file in the case where `coding-system-for-write'
is bound to the coding system `raw-text' for example, CRLF is
used as the line break code.  It is said that it happens as well
when communicating with an external process.

Because the default value of `nnmail-file-coding-system' and
`nnmail-active-file-coding-system' is `raw-text', the nnml back
end saves mail files, NOV files and the ACTIVE file as if the
coding-system is set to `raw-text-dos'.  Hideyuki SHIRAI said
that LF was used for the line break code formerly.  It might be
generally a good idea to use CRLF when saving files on Windows,
though.

You might not seem that it causes a problem since Gnus reads
those files using `raw-text' and CRLF is converted into LF again.
However, OHASHI Akira reported that a problem occurs actually.
He tried setting `gnus-nov-is-evil' to t and saw all summary
lines in a nnml group appeared as:

   [   ?: nobody                 ] (none)

I guess it always happens in nnmh groups.  Could anyone who uses
the most recent Emacs 22 built on Windows verify it?

The cause is that the `nnheader-insert-head' function doesn't
work properly.  In that function, it is expected that
`(insert-file-contents FILE nil BEG END)' returns `(FILE CHARS)',
where CHARS is the number in which BEG is subtracted from END.
However, it fails because of the CRLF-to-LF conversion.

I don't use Emacs on Windows, so I hope someone follows it up.
Here's a solution, though I haven't tested it yet.


[-- Attachment #2: Type: application/emacs-lisp, Size: 992 bytes --]

[-- Attachment #3: Type: text/plain, Size: 10 bytes --]


Regards,