From: Sam Steingold <sds@gnu.org>
To: ding@gnus.org
Subject: wrong score file is used
Date: Thu, 20 Oct 2022 10:26:46 -0400 [thread overview]
Message-ID: <lzfsgjtj8l.fsf@3c22fb11fdab.ant.amazon.com> (raw)
I noticed that an article was scored wrongly, so I did `V t`
and discovered that the rule comes from the file "soc" that is not
intended for this group.
Playing with the settings revealed the culprit:
--8<---------------cut here---------------start------------->8---
(add-hook 'gnus-score-find-score-files-function 'sds-gnus-upscore-new-thread)
(defun sds-gnus-upscore-new-thread (group)
"Up-score thread-starters in all groups with _discussions_.
Exclude `news` groups where there are no threads."
(and (not (string-match (concat "\\." (regexp-opt '("news" "slashdot" "announce" "stackexchange" "stackoverflow" "reddit"))) group))
'("new-thread")))
--8<---------------cut here---------------end--------------->8---
when I remove `sds-gnus-upscore-new-thread' from
`gnus-score-find-score-files-function', the scores are correct (minus
"new-thread" - which is, correctly, _not_ applied), but when I do add
`sds-gnus-upscore-new-thread' to `gnus-score-find-score-files-function',
I get _both_ "new-thread" and "soc" rules (and no, these files do not
reference each other)
I wonder if there is an easy way to debug this.
Setting `gnus-verbose' to 10 does not produce useful messages, just
"Scoring...done".
Ideally, I would like to see something like
"applying rules from file 'foo' because of ..."
Thank you.
--
Sam Steingold (https://aphar.dreamwidth.org/) on darwin Ns 10.3.2113
https://lastingimpactpsychology.com https://steingoldpsychology.com
http://think-israel.org https://jihadwatch.org https://mideasttruth.com
Programming is like sex: one mistake and you have to support it for a lifetime.
next reply other threads:[~2022-10-20 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 14:26 Sam Steingold [this message]
2022-10-20 15:29 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lzfsgjtj8l.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).