In news.software.readers, Kenny McCormack <gaz...@shell.xmission.com
> 2) There was nothing in either killfile that had to do with
> the memorization of this thread. I can tell this by the access
> date/time on the killfile file and/or by comparing the file (via
> the "diff" utility) to a previous version of it. I can state with
> pretty close to total certainty, that there's nothing in either
> file having to do with this memorization stuff.
I think there are three places it could be. Global killfile I do not
think is ever added to by trn, you have to edit it manually.
(Corrections welcome.) Group killfiles can be added by commands in the
newreader, and edited by typing <ctrl-k> at article selection level. I
use this, and I think this is likely the most commonly used filtering
in trn. Where those live is configurably, but it defaults to (eg)
~/News/news/software/readers/KILL . It is not easy to do _accidentally_
add rules there.
Third case, and easiest to accidentally trigger, is the scoring rules,
backported from some some trn fork, and not well documented. The default
location for those is ~/.trn/savedscores .
[ Examing code, I see there is another filtering/scoring system in trn,
but that one is even less likely to be accidentally triggered, as you
have to first configure a filter script. Those ones apparently get
saved as (eg) ~/News/Filters/News.software.readers ]
I don't really know the format of the savedscores files, I have some 200
lines in mine. It _appears_ to take a format like:
Where the .rules line may or may not exist. I think after the article
with the number expires, the rules become moot. If your news server
doesn't expire articles, probably removing the triplet of lines would
work, or just dropping the dot line with the rules.
Or you, know, just delete the whole savedscores file.
mostly has rulesets without dot lines