From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Sparse threads
Date: 08 Jan 1996 13:08:19 +0100 [thread overview]
Message-ID: <68emvqh8.fsf@bjob.no> (raw)
I thought filling in "gaps" in threads (without reading further
headers) would be a) a major project and b) slow as hell, but it
turned out to be quite simple to do. Just some References munging,
some sorting (since Message-IDs late in the References headers are
probably more reliable (with regards to what sequence articles have
been posted) than early Message-IDs), and some threading.
Before:
---------------
[ 52: Egil Kvaleberg ] Re: Redaktoransvar
[ 47: Erik Naggum ]
[ 25: Steinar Bang ]
< 16: Gisle Hannemyr >
[ 14: Willy Verwoerd ]
---------------
After:
---------------
Q [ 0: ] Re: Redaktoransvar
[ 52: Egil Kvaleberg ]
[ 47: Erik Naggum ]
[ 25: Steinar Bang ]
Q [ 0: ]
[ 16: Gisle Hannemyr ]
[ 14: Willy Verwoerd ]
---------------
The two articles that are marked with "Q" are the new "gaps" inserted
to fill out the thread. They can't be selected.
On the other hand -- Gnus does know the Message-ID of the "gap"
articles, so it could just fire off a request-by-id command? Yup, I
think I'll add that.
(14 features left on the todo list -- but they all require access to a
Real Computer to write, I think. `open-network-stream', etc. Curse
you, Windos '95!)
--
Lars Magne Ingebrigtsen * larsi@ifi.uio.no
(a red leaf that falls from the purple tree)
next reply other threads:[~1996-01-08 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-08 12:08 Lars Magne Ingebrigtsen [this message]
1996-01-10 18:41 ` Per Abrahamsen
1996-01-11 21:25 ` Lars Magne Ingebrigtsen
1996-01-19 13:15 ` Greg Stark
1996-01-20 5:25 ` Lars Magne Ingebrigtsen
1996-01-20 14:09 ` Greg Stark
1996-01-20 22:07 ` d. hall
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
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=68emvqh8.fsf@bjob.no \
--to=larsi@ifi.uio.no \
/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).