Score variable gnus-update-score-entry-dates

Score variable gnus-update-score-entry-dates

[Harry Putnam]

How is this variable used?  It really isn't clear in the
manual what gets matched or how.  I see no example.  The customization page
provides no clues either.

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

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

[Lars Magne Ingebrigtsen]

Harry Putnam <reader@newsguy.com> writes:

> How is this variable used?  It really isn't clear in the
> manual what gets matched or how.  I see no example.  The customization page
> provides no clues either.
>
> `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.  :-)

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

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

[Harry Putnam]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> How is this variable used?  It really isn't clear in the
>> manual what gets matched or how.  I see no example.  The customization page
>> provides no clues either.
>>
>> `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?  

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

[Lars Magne Ingebrigtsen]

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

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

[Harry Putnam]

[-- Attachment #1: Type: text/plain, Size: 450 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

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

Ahaa so `match' = `triggered' .  That makes sense now.  Maybe a tiny
patch is in order. (Hope I did that right..(i.e.  
   diff -u gnus.texi gnus.texi.edited >gnus.texi.diff))


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: match = trigger --]
[-- Type: text/x-patch, Size: 1033 bytes --]

--- gnus.texi	Sat Jan  5 10:02:10 2002
+++ gnus.texi.new	Sat Jan  5 10:20:56 2002
@@ -17025,12 +17025,12 @@
 
 @item gnus-update-score-entry-dates
 @vindex gnus-update-score-entry-dates
-If this variable is non-@code{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 @code{nil},
-even matching entries will grow old and will have to face that oh-so
-grim reaper.
+If this variable is non-@code{nil}, temporary score entries that have
+been triggered (matched) will have their dates updated.  (This is how Gnus
+controls expiry---all non-matched-entries will become too old while
+matched entries will stay fresh and young.)  However, if you set this
+variable to @code{nil}, even matched entries will grow old and will
+have to face that oh-so grim reaper.
 
 @item gnus-score-after-write-file-function
 @vindex gnus-score-after-write-file-function

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

[Lars Magne Ingebrigtsen]

Harry Putnam <reader@newsguy.com> writes:

> Ahaa so `match' = `triggered' .  That makes sense now.  Maybe a tiny
> patch is in order. (Hope I did that right..(i.e.  
>    diff -u gnus.texi gnus.texi.edited >gnus.texi.diff))

Yeah, that's the way to do it.

Thanks for the patch; I've applied it to Oort Gnus v0.05 (i. e., CVS).

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