Gnus development mailing list
 help / color / mirror / Atom feed
* The adaptive score alist variables.
@ 2010-07-03  9:33 Štěpán Němec
  2010-07-07 17:13 ` Ted Zlatanov
  0 siblings, 1 reply; 3+ messages in thread
From: Štěpán Němec @ 2010-07-03  9:33 UTC (permalink / raw)
  To: ding


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




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: The adaptive score alist variables.
  2010-07-03  9:33 The adaptive score alist variables Štěpán Němec
@ 2010-07-07 17:13 ` Ted Zlatanov
  2010-08-28 22:40   ` Lars Magne Ingebrigtsen
  0 siblings, 1 reply; 3+ messages in thread
From: Ted Zlatanov @ 2010-07-07 17:13 UTC (permalink / raw)
  To: ding

On Sat, 03 Jul 2010 11:33:39 +0200 Štěpán Němec <stepnem@gmail.com> wrote: 

ŠN> Is this difference (symbols in one case, values in the other case)
ŠN> significant? If so, that looks like a horrible design. 

Looks like larsi did it (last related edits were in 1997), though I
don't know why.  Maybe it was for performance reasons.

ŠN> Also, why should I have to evaluate the mark symbols to actually get
ŠN> to know their numeric values and be able to adjust the word score
ŠN> alist? (I understand the marks are character values, but the
ŠN> correspondence is not obvious, esp. when `describe-variable' gives
ŠN> you the numeric values.)

You shouldn't have to, normally.  Maybe it just wasn't meant as a
long-term solution.  Sorry I don't know more.

Ted




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: The adaptive score alist variables.
  2010-07-07 17:13 ` Ted Zlatanov
@ 2010-08-28 22:40   ` Lars Magne Ingebrigtsen
  0 siblings, 0 replies; 3+ messages in thread
From: Lars Magne Ingebrigtsen @ 2010-08-28 22:40 UTC (permalink / raw)
  To: ding

Ted Zlatanov <tzz@lifelogs.com> writes:

> ŠN> Also, why should I have to evaluate the mark symbols to actually get
> ŠN> to know their numeric values and be able to adjust the word score
> ŠN> alist? (I understand the marks are character values, but the
> ŠN> correspondence is not obvious, esp. when `describe-variable' gives
> ŠN> you the numeric values.)
>
> You shouldn't have to, normally.  Maybe it just wasn't meant as a
> long-term solution.  Sorry I don't know more.

I can't recall, either.  Might be some ... legacy reason...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-08-28 22:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-03  9:33 The adaptive score alist variables Štěpán Němec
2010-07-07 17:13 ` Ted Zlatanov
2010-08-28 22:40   ` Lars Magne Ingebrigtsen

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).