From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/38778 Path: main.gmane.org!not-for-mail From: Samuel Padgett Newsgroups: gmane.emacs.gnus.general Subject: Re: wrong-type-argument exiting nnml group Date: Sat, 15 Sep 2001 16:56:31 -0400 Sender: Samuel Padgett Message-ID: <87pu8sxjeo.fsf@harpo.homeip.net> References: <87g09oz88k.fsf@harpo.homeip.net> <87u1y4xovs.fsf@harpo.homeip.net> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035174587 24271 80.91.224.250 (21 Oct 2002 04:29:47 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:29:47 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 2095 invoked from network); 15 Sep 2001 20:55:53 -0000 Original-Received: from rdu57-93-009.nc.rr.com (HELO harpo.homeip.net) (66.57.93.9) by gnus.org with SMTP; 15 Sep 2001 20:55:53 -0000 Original-Received: from sam by harpo.homeip.net with local (Exim 3.32 #1 (Debian)) id 15iMUJ-0005o9-00 for ; Sat, 15 Sep 2001 16:56:31 -0400 Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Sat, 15 Sep 2001 21:48:18 +0200") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.105 Original-Lines: 27 Xref: main.gmane.org gmane.emacs.gnus.general:38778 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:38778 Simon Josefsson writes: > Samuel Padgett writes: > >> Hm. Looking at it after nnml-generate-nov-databases, I see that there >> is a ^M after each header field for article 1. Could this have caused >> the problem? > > Yes. I do not understand how that happens though, even if the article > in question uses CRLF the NOV parsing routine isn't fooled, at least > for me. I looked at the article more closely and noticed it has mixed line endings. The first four lines end with just a LF, whereas the rest end with CRLF. > If you edebug `nnml-generate-nov-file', does the *nntpd* buffer > contain ^M's after the call to `nnheader-insert-file-contents'? It > doesn't for me, and I suspect it is a feature but I'm not sure why it > happens. Yes, the *nntpd* buffer contains the ^M's. I'm sure it's because of the mixed line endings, though. Sam -- May all your PUSHes be POPped.