Re: weirdness wrt file-coding

[Adrian Aichner <aichner@ecf.teradyne.com>]

>>>>> "Fabrice" == Fabrice POPINEAU <popineau@ese-metz.fr> writes:

    Fabrice> Hi,

    Fabrice> Using xemacs-21.0b57 and xemacs-21.2b5 (NT, compiled
    Fabrice> natively), I can only report weirdness due to incorrect
    Fabrice> file type guessing or conversion in gnus.  I'm using
    Fabrice> pgnus-0.65. The file retrieved by movemail is put into
    Fabrice> ~/.gnus-crash-box and parsed in the buffer named "
    Fabrice> *nnmail incoming*".

    Fabrice> But the parsing fails before the end of the file
    Fabrice> (function nnmail-process-babyl-mail-format,
    Fabrice> re-search-forward returns nil, delete-region is then
    Fabrice> called with 0 :-( ).

    Fabrice> Switching to the buffer shows that there are '^M' at the
    Fabrice> end of each line.  Toggling the file coding to 'noconv'
    Fabrice> manually, and then rewriting .gnus-crash-box enables to
    Fabrice> read the messages correctly next time gnus is run.

    Fabrice> It acts like if the file was read in text mode, but the
    Fabrice> conversion binary -> text failed, and the specified
    Fabrice> file-coding is text anyway.

    Fabrice> At first, I thought it was apel playing with file-coding,
    Fabrice> and that just removing 'tm' use from gnus-setup would do
    Fabrice> the trick. But unfortunately, there is a deeper problem.

This was my first thought too.

Seems like (emacs-version) "XEmacs 21.0 \"Poitou59\" [Lucid]
(i386-pc-win32) of Wed Dec 09 1998 on DARTER2"
does not cooperate with EFS either.

More later...

Adrian