From: yeti <yeti@tilde.institute>
To: ding@gnus.org
Subject: Re: Score articles that supersede older articles in nntp
Date: Wed, 06 Dec 2023 17:15:59 +0000 [thread overview]
Message-ID: <87jzprntf4.fsf@tilde.institute> (raw)
In-Reply-To: <87r0jz5kyq.fsf@tullinup.koldfront.dk>
I couldn't get it done via gnus-extra-headers, but scanning all headers
for "^Supersedes: " seems to work.
------------------------------------------------------------------------
(("head"
("^Supersedes: " 4711 nil r)))
------------------------------------------------------------------------
=>
------------------------------------------------------------------------
O 20230417T092214 [yeti ][ 4711] playing with GNUS
OA 20230421T142311 [yeti ][ 0] > ţęşţ
O 20230429T135320 [yeti ][ 0] +->
OA 20230429T135713 [yeti ][ 4711] \->
O 20230429T140909 [yeti ][ 0] \->
------------------------------------------------------------------------
But it scans slooooooow...
--
1. Hitchhiker 25: (76) "How long?" he said. (77) "Seven and a half
million years," said Deep Thought. (78) Lunkwill and Fook blinked at
each other. (79) "Seven and a half million years ...!" they cried in
chorus.
next prev parent reply other threads:[~2023-12-06 18:28 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 [this message]
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=87jzprntf4.fsf@tilde.institute \
--to=yeti@tilde.institute \
--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).