From: Fabrice POPINEAU <popineau@ese-metz.fr>
Cc: ding@gnus.org
Subject: weirdness wrt file-coding
Date: 09 Dec 1998 14:26:15 +0100 [thread overview]
Message-ID: <ulnkh4fbc.fsf@ese-metz.fr> (raw)
Hi,
Using xemacs-21.0b57 and xemacs-21.2b5 (NT, compiled natively), I can
only report weirdness due to incorrect file type guessing or
conversion in gnus. I'm using pgnus-0.65. The file retrieved by
movemail is put into ~/.gnus-crash-box and parsed in the buffer named
" *nnmail incoming*".
But the parsing fails before the end of the file (function
nnmail-process-babyl-mail-format, re-search-forward returns nil,
delete-region is then called with 0 :-( ).
Switching to the buffer shows that there are '^M' at the end of each
line. Toggling the file coding to 'noconv' manually, and then
rewriting .gnus-crash-box enables to read the messages correctly next
time gnus is run.
It acts like if the file was read in text mode, but the conversion
binary -> text failed, and the specified file-coding is text anyway.
At first, I thought it was apel playing with file-coding, and that
just removing 'tm' use from gnus-setup would do the trick. But
unfortunately, there is a deeper problem.
--
Fabrice POPINEAU
------------------------
e-mail: popineau@ese-metz.fr | "God is real ...
Fabrice.POPINEAU@supelec.fr |
voice-mail: +33 (0) 387764715 | ... unless integer ?"
surface-mail: Supelec, 2 rue E. Belin, |
F-57078 Metz Cedex 3 |
next reply other threads:[~1998-12-09 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-09 13:26 Fabrice POPINEAU [this message]
1998-12-09 18:58 ` Shenghuo ZHU
1998-12-14 13:29 ` Fabrice POPINEAU
[not found] <162AE4075794A2D6852566D5006B60E1.004BF1EF802566D5@notes.teradyne.com>
1998-12-09 16:52 ` Adrian Aichner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ulnkh4fbc.fsf@ese-metz.fr \
--to=popineau@ese-metz.fr \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).