Re: Score variable gnus-update-score-entry-dates

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Harry Putnam <reader@newsguy.com> writes:

>>> `gnus-update-score-entry-dates'
>>>      If this variable is non-`nil', matching score entries will have
>>>      their dates updated.  (This is how Gnus controls expiry--all
>>>      non-matching entries will become too old while matching entries
>>>      will stay fresh and young.)  However, if you set this variable to
>>>      `nil', even matching entries will grow old and will have to face
>>>      that oh-so grim reaper.
>>>
>>> Is this applicable only to scores defined as `temporary'.  This really
>>> needs some elaboration in the manual, I think.
>>
>> Probably; yes.  But I'm not quite sure how to elaborate -- only
>> temporary score entries are, er, temparorary.  The permanent ones are,
>> like, permanent.  :-)
>
> Its bad manners to chide a retard.... :-)
>
> What about the matching Mr. Smarty pants. :-)  What is it that gets
> matched, how is the regexp inserted?  

Oh, right.  That's not very clear.

If a score entry "match" -- for some value of "match" -- then the
thing that's described above happens.  You can score on many different
things, but if a score rule is triggered, we call that a "match".  So
the text above talks about what happens (or not) to score rule entries
depending on whether they were triggered or not.

So `gnus-update-score-entry-dates' really determines how temporary
score rule entries are aged.  If nil, all temporary score rule entries
are aged.  If non-nil, only the non-triggered score rule entries are
aged. 

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