Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <>
Subject: Re: Score articles that supersede older articles in nntp
Date: Sat, 09 Dec 2023 00:12:17 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Tracing through this, it seems the lines returned from XOVER gets
parsed by nnheader-parse-nov which uses a macro
nnheader-nov-parse-extra which just returns nil, even though LIST
OVERVIEW.FMT specified an extra field after Xref, and even though
XOVER sent that field.

Not quite sure what kind of surgery is needed to improve this.

Oh, wait, it expects the extra fields to be prefixed with the header
name, like Xref: is?

Let me try that.

YES, that was it!

John: try this score rule on now:

  (("extra" ("." -1000 nil r "Supersedes")))


  Best regards,


 "The code is more what you'd call 'guidelines',            Adam Sjøgren
  than actual rules."                        

  reply	other threads:[~2023-12-08 23:12 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
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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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