From: Ted Zlatanov <tzz@lifelogs.com>
Subject: (gnus-data-list nil) does not give valid data sometimes
Date: Thu, 08 Jan 2004 17:51:32 -0500 [thread overview]
Message-ID: <4nr7yagikr.fsf@collins.bwh.harvard.edu> (raw)
The function that fails is:
(defun spam-fetch-field-fast (article field)
"Fetch a field quickly, using the internal gnus-data-list function"
(when (numberp article)
(gnus-get-newsgroup-headers)
(let* ((header (assoc article (gnus-data-list nil)))
(data-header (if header (gnus-data-header header) nil)))
(if (arrayp data-header)
(cond
((equal field 'from)
(mail-header-from data-header))
((equal field 'message-id)
(mail-header-message-id data-header))
((equal field 'subject)
(mail-header-subject data-header))
((equal field 'references)
(mail-header-references data-header))
((equal field 'date)
(mail-header-date data-header))
((equal field 'xref)
(mail-header-xref data-header))
((equal field 'extra)
(mail-header-extra data-header))
(t
nil))
(gnus-error 5 "Article %d has a nil data header" article)))))
When entering a group the first time, lots of errors are generated
above because data-header is nil. After C-g, the next time the group
is entered everything is fine. BUT the next time (3rd time) the
group is entered, the errors happen again - and so on, this can be
repeated forever. I don't use the agent - I'm not sure what's wrong.
This, by the way, is called by spam-insert-fake-headers which is
called by spam-find-spam; spam-find-spam is hooked on
gnus-summary-prepare-hook.
Thanks
Ted
next reply other threads:[~2004-01-08 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 22:51 Ted Zlatanov [this message]
2004-01-09 0:58 ` Ted Zlatanov
2004-01-09 18:43 ` bug/feature?: gnus-data-list is not ready in gnus-summary-prepare-hook (was: (gnus-data-list nil) does not give valid data sometimes) Ted Zlatanov
2004-01-09 21:41 ` bug/feature?: gnus-data-list is not ready in 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=4nr7yagikr.fsf@collins.bwh.harvard.edu \
--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).