Gnus development mailing list
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@gmail.com>
To: ding@gnus.org
Subject: The adaptive score alist variables.
Date: Sat, 03 Jul 2010 11:33:39 +0200	[thread overview]
Message-ID: <87iq4w3o5o.fsf@gmail.com> (raw)


In (info "(gnus)Adaptive Scoring") there is a strange discrepancy
between `gnus-default-adaptive-score-alist' and
`gnus-default-adaptive-word-score-alist'.

While the former is exemplified as

      '((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-ancient-mark)
         (gnus-low-score-mark)
         (gnus-catchup-mark (from -1) (subject -1))))

the latter is shown as

     `((,gnus-read-mark . 30)
       (,gnus-catchup-mark . -10)
       (,gnus-killed-mark . -20)
       (,gnus-del-mark . -15)))

And indeed, the default value of g-d-a-w-s-a is

    '((82 . 30)
      (67 . -10)
      (75 . -20)
      (114 . -15))

Is this difference (symbols in one case, values in the other case)
significant? If so, that looks like a horrible design. Also, why
should I have to evaluate the mark symbols to actually get to know their
numeric values and be able to adjust the word score alist? (I understand
the marks are character values, but the correspondence is not obvious,
esp. when `describe-variable' gives you the numeric values.)

Štěpán




             reply	other threads:[~2010-07-03  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  9:33 Štěpán Němec [this message]
2010-07-07 17:13 ` Ted Zlatanov
2010-08-28 22:40   ` 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=87iq4w3o5o.fsf@gmail.com \
    --to=stepnem@gmail.com \
    --cc=ding@gnus.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).