From: IPmonger <ipmonger@delamancha.org>
Subject: Help with adaptive scoring problems
Date: Thu, 21 Feb 2002 02:42:39 -0500 [thread overview]
Message-ID: <m34rkbxrn6.fsf@cornelius.delamancha.org> (raw)
Folks,
Here's my definition of gnus-default-adaptive-score-alist (load from .gnus.el):
(defvar gnus-default-adaptive-score-alist
'((gnus-unread-mark (thread 10))
(gnus-ticked-mark (from 4))
(gnus-dormant-mark (from 5))
(gnus-del-mark (from -4) (subject -1) (thread -1))
(gnus-read-mark (from 4) (subject 2) (thread 25))
(gnus-expirable-mark)
(gnus-killed-mark (from -10) (subject -3))
(gnus-kill-file-mark)
(gnus-ancient-mark)
(gnus-low-score-mark)
(gnus-catchup-mark (from -1) (subject -1))))
When I have this defined, I can not exit from a *Summary* buffer
correctly, due to an unbound symbol 'thread
gnus-score-adaptive (gnus-score.el, line:2181) is not correctly
handling the (thread <score-delta>) elements of the above alist:
On line 2211, the string "mail-header-thread" is looked up in
obarray, not found, so a new (unbound) symbol mail-header-thread is
created.
Since it is unbound, (fboundp ...) (line 2212) is nil, which means
that we
skip down to line 2224 - which preserves the
(thread <score-delta>) form and then go on with the conversion of
the alist.
Now, when we get down to line 2234 - to begin scoring - we end up
with (funcall thread headers), but 'thread is unbound! Yow!
Any help with figuring out where this is *supposed* to be set
would be appreciated. I'm running Oort 0.06 updated from CVS at
00:58 EST on 2002-02-21.
-IPmonger
--
------------------
IPmonger
ipmonger@delamancha.org
next reply other threads:[~2002-02-21 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 7:42 IPmonger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 7:42 IPmonger
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=m34rkbxrn6.fsf@cornelius.delamancha.org \
--to=ipmonger@delamancha.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).