On Sat, 24 May 1997 22:03:45 +0100,
In article <xe1hzcun8P3I092yn@swol.de>, rgriech@swol.de (Hardy Griech) wrote:
> On Sat, 24 May 1997 12:18:55 -0500, bobr@mcs.com (Robert P. Rush) wrote:
> :
> > > I experimented this alternative. It didn't work for me. VSoup errored out
> > > and aborted using the score file. The questioned is the killthreshold
> > > line within { }. I rechecked vsoup.inf. Does every score-rule need be
> > > preceded with a score ? or killthreshold must be global?
> >
> > I'm sorry, I thought you were using Souper. That is the correct
> > syntax for Souper. From What I could tell from the VSoup
> > documentation, the killthreshold line must be placed outside of any
> > set of braces { }.
> :
>
> Yes, VSoup only has one single global killthreshold. This might be
> seen as a limitation, but on the other hand, one can specify the
> kill-group with a regular expression. And this feature makes it
> impossible to have group-killthresholds.
>
> Imagine you have a killgroup 'os2' with a local killthreshold of '-5'
> and another killgroup 'binaries' with a local killthreshold of '-1'.
> How should VSoup decide, if it checks 'comp.os.os2.binaries'?
You could stick with the rule that the last killthreshold seen is
used.
1. If no local killthreshold is used, the last global killthreshold
in the file is used.
2. If one or more local killthresholds apply, the last local
killthreshold that applies will be used.
Thus for the following score file, 'comp.os.os2.binaries' would have a
killthreshold of 3, 'comp.os.windows.binaries' would have a kill
threshold of 2, and 'alt.usenet.offline-reader' would have a
killthreshold of 4.
---------------------
killthreshold 1
binaries {
killthreshold 2
}
os2 {
killthreshold 3
}
killthreshold 4
--------------------
>
> > According to the VSoup documentation, every score rule does need to be
> > preceded by a number.
>
> Correct.
>
> > If you want to apply a killthreshold to a specific group, the "-1
> > Subject: $" seems to be the only way, although, you might want to
> > change the '$' to a '^'. That way, it'll look for the beginning of the
> > line instead of the end of the line. It may speed it up just a tad.
> :
>
Actually, I meant "1 pattern Subject: $", although your suggestions of
"1 Subject:" or "1 Lines: > 0" would be a better idea since it
wouldn't use regular expressions. Hopefully, that should teach me
about checking and double checking my answers.
> Hardy
>
> --
> Hardy Griech, Ernetstr. 10/1, D-77933 Lahr
> http://privat.swol.de/ReinhardGriech/
>
Talk with you later,
bob
-- Bob Rush | eschew obfuscation bobr@mcs.com | <http://www.mcs.com/~bobr/> |If two million people do a foolish thing, it's still a foolish thing.