Gnus development mailing list
 help / color / mirror / Atom feed
From: Nelson Ferreira <nelson.ferreira@verizon.net>
Subject: [PATCH] Problems accessing spam group (again)
Date: Tue, 08 Jun 2004 01:13:00 -0400	[thread overview]
Message-ID: <45898.3762459413$1086671720@news.gmane.org> (raw)


Intermitently I've been getting the following error:

Signaling: (wrong-type-argument arrayp nil)
  gnus-dup-unsuppress-article(35829)
  gnus-mark-article-as-unread(35829 ?$)
  gnus-summary-mark-article(35829 ?$)
  spam-mark-junk-as-spam-routine()
  spam-summary-prepare()
  run-hooks(spam-summary-prepare)
  apply(run-hooks spam-summary-prepare)
  gnus-run-hooks(gnus-summary-prepare-hook)
  gnus-summary-prepare()
  gnus-summary-read-group-1("nnml:mail.spam" nil t nil nil nil)
  gnus-summary-read-group("nnml:mail.spam" nil t nil nil nil nil)
  gnus-group-read-group(nil t)
  gnus-group-select-group(nil)
  gnus-topic-select-group(nil)
  call-interactively(gnus-topic-select-group)

I traced it to gnus-dup-unsuppress-article being called when
gnus-dup-hashtb is not an array.

I fixed it with the following (trivial) patch, although not sure if it
is the solution to the real problem:

diff -u -r7.3 gnus-dup.el
--- gnus-dup.el 20 May 2004 08:02:39 -0000      7.3
+++ gnus-dup.el 8 Jun 2004 05:11:27 -0000
@@ -156,7 +156,7 @@
   "Stop suppression of ARTICLE."
   (let* ((header (gnus-data-header (gnus-data-find article)))
         (id     (when header (mail-header-id header))))
-    (when id
+    (when (and id gnus-dup-hashtb)
       (setq gnus-dup-list-dirty t)
       (setq gnus-dup-list (delete id gnus-dup-list))
       (unintern id gnus-dup-hashtb))))


-- 
Nelson Ferreira



                 reply	other threads:[~2004-06-08  5:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='45898.3762459413$1086671720@news.gmane.org' \
    --to=nelson.ferreira@verizon.net \
    /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).