Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: error in current CVS
Date: Tue, 22 Apr 2003 09:10:57 -0400	[thread overview]
Message-ID: <m3of2y8you.fsf@heechee.beld.net> (raw)
In-Reply-To: <vz1xzv86fl.fsf@viteno.dyns.net> (Norbert Koch's message of "Tue, 22 Apr 2003 07:09:02 +0200")

On Tue, 22 Apr 2003, nk@viteno.net wrote:
> Using Oort Gnus v0.19, CVS updated an hour ago, I'll get the
> following error when I try to select my spam group, ie the one I
> split spam into using spam.el (in combination with bogofilter).
> This is the only group I see this behaviour:
> 
> Signaling: (wrong-type-argument arrayp nil)
>   gnus-dup-unsuppress-article(552)
>   gnus-mark-article-as-unread(552 ?$)
>   gnus-summary-mark-article(552 ?$)
>   spam-mark-junk-as-spam-routine()

Up to spam-mark-junk-as-spam-routine this is triggered by spam.el
using the list of articles from gnus-newsgroup-unreads or
gnus-newsgroup-unseen, but the error with gnus-dup-unsuppress-article
is outside spam.el, in gnus-dup.el.  I think the arrayp error is
happening when gnus-dup-unsuppress-article runs

(gnus-data-header (gnus-data-find article))

and the article is somehow not available.  I recently switched from
running through all the articles sequentially to using
gnus-newsgroup-unseen and gnus-newsgroup-unreads in
spam-mark-junk-as-spam-routine, could that be the problem?

Ted




  reply	other threads:[~2003-04-22 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22  5:09 Norbert Koch
2003-04-22 13:10 ` Ted Zlatanov [this message]
2003-04-22 14:26   ` Norbert Koch
2003-04-22 16:05     ` gnus-newsgroup-unseen gives gnus-dup-unsuppress-article error (was: error in current CVS) Ted Zlatanov
2003-04-23  5:35       ` gnus-newsgroup-unseen gives gnus-dup-unsuppress-article error Kevin Greiner
2003-04-23 11:39         ` Ted Zlatanov
2003-04-23 17:50           ` Norbert Koch

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=m3of2y8you.fsf@heechee.beld.net \
    --to=tzz@lifelogs.com \
    /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).