Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Dave Abrahams <dave@boostpro.com>
Cc: <9208@debbugs.gnu.org>, Ding Mailing List <ding@gnus.org>
Subject: Re: bug#9208: article has a nil data header
Date: Tue, 24 Jan 2012 16:40:30 -0600	[thread overview]
Message-ID: <87obtsiv1d.fsf@lifelogs.com> (raw)
In-Reply-To: <m3r556a0nf.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 31 Jul 2011 18:13:40 +0200")

On Sun, 31 Jul 2011 18:13:40 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote: 

LMI> Dave Abrahams <dave@boostpro.com> writes:
>> Naturally I have no idea how I got here and no confidence that I can
>> reproduce it, but this just appeared in my *Messages* buffer.  I thought
>> someone should know.
>> 
>> Mark all unread articles as read? (y or n) 
>> Exiting summary buffer and applying spam rules
>> Article 52 has a nil data header
>> Article 45 has a nil data header
>> Article 39 has a nil data header

LMI> Ted probably knows what this means.  :-)  Ted?

My guess is that Dave had multiple summary buffers open and spam.el
doesn't keep separate article lists per summary buffer.  So on exit,
spam.el tried to look up missing articles.

See my earlier e-mail on the topic of spam2.el.

Ted



       reply	other threads:[~2012-01-24 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2fwlnp6hd.fsf@pluto.luannocracy.com>
     [not found] ` <m3r556a0nf.fsf@stories.gnus.org>
2012-01-24 22:40   ` Ted Zlatanov [this message]
2012-09-05 18:05     ` Lars Ingebrigtsen
2012-09-05 19:44       ` Dave Abrahams
2012-09-17 19:07       ` Dave Abrahams
2012-12-22 20:16         ` Ted Zlatanov

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=87obtsiv1d.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=9208@debbugs.gnu.org \
    --cc=dave@boostpro.com \
    --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).