From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: griffith@filippo.sfs.nphil.uni-tuebingen.de
Subject: Confused about g-d-adaptive-score-alist manual description
Date: Sat, 17 Feb 1996 12:57:39 +0100 [thread overview]
Message-ID: <199602171157.MAA04919@filippo.sfs.nphil.uni-tuebingen.de> (raw)
The manual gives the following example:
----------------------------------------------------------------------
(defvar gnus-default-adaptive-score-alist
'((gnus-unread-mark)
(gnus-ticked-mark (from 4))
(gnus-dormant-mark (from 5))
(gnus-del-mark (from -4) (subject -1))
(gnus-read-mark (from 4) (subject 2))
(gnus-expirable-mark (from -1) (subject -1))
(gnus-killed-mark (from -1) (subject -3))
(gnus-kill-file-mark)
(gnus-catchup-mark (from -1) (subject -1))))
As you see, each element in this alist has a mark as a key (either a
variable name or a "real" mark--a character). Following this key is a
random number of header/score pairs.
----------------------------------------------------------------------
What does a element of this list do if has NO header/score pairs? For
instance, what does `(gnus-unread-mark)' do? This does not seem to be
addressed.
Also, other questions include:
1) If more than one element applies to an article, are all
header/score pairs used? (I assume they are). For instance, if
an article is both read and marked dormant will the author get
raised 4+5 = 9 points?
2) If several messages have the same subject (or the same author)
will the scoring rules be applied multiple times? For instance,
if there are 26 articles in some thread which I didn't read but
catchup'd, would that subject be decreased by -1 or -26 points?
3) A list of all (reasonable) marks would be useful too.
next reply other threads:[~1996-02-17 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-17 11:57 John Griffith [this message]
1996-02-17 14:21 ` Lars Magne Ingebrigtsen
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=199602171157.MAA04919@filippo.sfs.nphil.uni-tuebingen.de \
--to=griffith@sfs.nphil.uni-tuebingen.de \
--cc=griffith@filippo.sfs.nphil.uni-tuebingen.de \
/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).