After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 113771 - Anomalous scoring in watched threads.
Anomalous scoring in watched threads.
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
0.14.0
Other Linux
: Normal normal
: 0.14.1
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2003-05-26 22:13 UTC by Bobby D. Bryant
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bobby D. Bryant 2003-05-26 22:13:01 UTC
When scoring watched threads, the final score for an article depends on the
ordering of the entries in your scorefile.

This is apparently because "watch" sets score=9999, so that any scoring
done before that match is effectively overwritten, but any scoring done
after that match will still apply deltas to the 9999 set by the "watch".

I think the sensible and easy fix would be to set "watch" scoring to be a
delta of +9999 rather than an absolute =9999.

Thanks.
Comment 1 Charles Kerr 2003-07-14 01:44:09 UTC
I know that slrn has some mechanism for stopping scoring as soon
as 9999 or -9999 is reached, but I'll have to go back and read
slrn again to see how it works.
Comment 2 Charles Kerr 2003-07-15 05:51:35 UTC
slrn stops scoring after a = is reached...
Comment 3 Charles Kerr 2003-07-15 05:57:19 UTC
Yuk, this is going to take some ugly changes to score.c to get in sync
with slrn. :)
Comment 4 Charles Kerr 2003-07-15 06:54:11 UTC
This is fixed in CVS:

http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan/pan/filters&command=DIFF_FRAMESET&file=score.c&rev1=1.16&rev2=1.17&root=/cvs/gnome

Because we stop once an assignment ('=') matches the article,
further scorefile entries that could apply deltas to take the
article below the `watch' threshold won't be reached.