Gnus development mailing list
 help / color / mirror / Atom feed
From: John Haman <mail@johnhaman.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Score articles that supersede older articles in nntp
Date: Tue, 05 Dec 2023 07:23:46 -0500	[thread overview]
Message-ID: <m1cyvkg7n1.fsf@johnhaman.org> (raw)
In-Reply-To: <875y1dtkov.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 04 Dec 2023 19:03:28 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

>
> 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...)
>

Thanks!

Unfortunately the rule

(("extra"
  ("Supersedes" -1000 nil s)))

Does not work either.

-- 
Dr. John Haman
Maryland, USA


  parent reply	other threads:[~2023-12-05 12:24 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
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 [this message]
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=m1cyvkg7n1.fsf@johnhaman.org \
    --to=mail@johnhaman.org \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).