From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Score articles that supersede older articles in nntp
Date: Mon, 04 Dec 2023 19:03:28 -0800 [thread overview]
Message-ID: <875y1dtkov.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m1r0k1fn2y.fsf@johnhaman.org>
John Haman <mail@johnhaman.org> writes:
> I realized the subject didn't match the intent of the question, adjusted...
>
>
> John Haman <mail@johnhaman.org> writes:
>
>> I would like to lower the score on nntp articles that superseded older articles.
>> I thought of two ways to do this, but they don't seem to work. Here is one of
>> the scoring rules that I tried. I added "Supercedes" to `gnus-extra-headers',
>>
>> Then I tried the scoring rule:
>>
>> (("extra"
>> ("" -1000 nil s "Supersedes"))
>>
>> (This is what I get from following the gnus prompts, I also tried
>>
>> (("extra"
>> ("Supercedes" -1000 nil s))
This might be an artifact of posting here, but you've got "Supersedes"
in one place, and "Supercedes" in the other. Looks like the "c" is the
correct spelling, maybe confirm that first? (The manual even makes a
snarky comment about this...)
next prev parent reply other threads:[~2023-12-05 3:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 23:49 Score articles that have been superseded John Haman
2023-12-05 1:35 ` Score articles that supersede older articles in nntp John Haman
2023-12-05 3:03 ` Eric Abrahamsen [this message]
2023-12-05 5:48 ` Adam Sjøgren
2023-12-05 15:09 ` Eric Abrahamsen
2023-12-05 15:16 ` Emanuel Berg
2023-12-05 12:23 ` John Haman
2023-12-05 13:12 ` Adam Sjøgren
2023-12-05 13:41 ` Adam Sjøgren
2023-12-06 0:46 ` John Haman
2023-12-06 16:55 ` Adam Sjøgren
2023-12-06 17:15 ` yeti
2023-12-07 2:53 ` John Haman
2023-12-08 22:17 ` Adam Sjøgren
2023-12-08 23:12 ` Adam Sjøgren
2023-12-09 1:41 ` John Haman
2023-12-09 19:00 ` John Haman
2023-12-09 21:12 ` Adam Sjøgren
2023-12-06 7:12 ` Score articles that have been superseded yeti
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=875y1dtkov.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).