From: Steinar Bang <sb@metis.no>
Subject: Puzzle: Why do some follow-ups thread and some not
Date: 14 Jun 1996 18:28:42 +0200 [thread overview]
Message-ID: <whvigu2vut.fsf@brage.metis.no> (raw)
Emacs 19.31, Gnus 5.2.14 (but this behaviour I've observed since 5.1)
What makes some articles in mail folders thread, and some not?
Articles made with a follow-up with Gnus seem to thread, articles
created with a reply in RMAIL seem to thread. Articles made with a
reply with Mew seem to thread.
Articles made with a reply with mh-e doesn't thread. Ditto for exmh.
I've created a replcomps file that gives me In-reply-to headers and
References headers.
At the start, I *think* I got these to thread, but then they suddenly
stopped threading.
But all of this may be caused by erronous headers. So here comes the
mysterious part:
I have two articles. One made by RMAIL (the one from Trond
Kristiansen), one made by mh-e (the one from me).
I've tried hand editing the one from me, to see if I could get it to
thread, and I've been unsuccessful in doing so.
I've done the testing by editing, then starting a new emacs, then
killing all Gnus buffers and exiting emacs, answering "yes" on the
"unsaved buffers exits, do you really...etc.". Then editing, and
starting a new emacs, answering "n" on the offer to use auto save
file (even when I've deleted "#.newsrc-dribble" it displays this
prompt).
So here are the two headers. As near as I can see, all headers that
should be relevant for threading are identical. But one thread and
the other doesn't.
This isn't like, important. But it really *bugs* me not knowing *why*
this happens...:-(
Is the information about the threading cached in some obscure place?
I've tried stripped everything relating to this mailing list out of
.newsrc.eld (without finding anything, when I refused the offer to
save).
Header 1
Replied: Fri, 14 Jun 1996 11:33:20 +0200
Replied: "Trond Kristiansen <tk@metis.no> dk,jh,lro,ht"
Return-Path: tk@metis.no
Received: by hub.metis.no (8.6.12/8.6.12) with ESMTP id MAA01848; Thu, 13 Jun 1996 12:30:31 +0200
Received: by client.metis.no (8.6.11/8.6.12) id MAA01099; Thu, 13 Jun 1996 12:30:29 +0200
Date: Thu, 13 Jun 1996 12:30:29 +0200
Message-Id: <199606131030.MAA01099@client.metis.no>
From: Trond Kristiansen <tk@metis.no>
To: dk@metis.no
CC: jh@metis.no, lro@metis.no, ht@metis.no, sb@metis.no, lro@metis.no
In-reply-to: <31BFDACB.2698@metis.no> (message from Dag Karlsen on Thu, 13 Jun
1996 11:09:31 +0200)
References: <31BFDACB.2698@metis.no>
Subject: Re: New 1.x API
Header 2
Received: by hub.metis.no (8.6.12/8.6.12) with ESMTP id LAA09768; Fri, 14 Jun 1996 11:16:27 +0200
Received: by client.metis.no (8.6.11/8.6.12) with ESMTP id LAA20466; Fri, 14 Jun 1996 11:16:26 +0200
Return-Path: sb@metis.no
Date: Fri, 14 Jun 1996 11:16:25 +0200
Message-Id: <199606140916.LAA20466@client.metis.no>
From: Steinar Bang <sb@metis.no>
To: Dag Karlsen <dk@metis.no>
CC: jh@metis.no, lro@metis.no, ht@metis.no, sb@metis.no, lro@metis.no
In-reply-to: <31BFDACB.2698@metis.no> (message from Dag Karlsen on Thu, 13 Jun
1996 11:09:31 +0200)
References: <31BFDACB.2698@metis.no>
Subject: Re: New 1.x API
next reply other threads:[~1996-06-14 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-14 16:28 Steinar Bang [this message]
1996-06-14 17:34 ` Jens Lautenbacher
1996-06-14 22:21 ` Sten Drescher
1996-06-14 22:55 ` 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=whvigu2vut.fsf@brage.metis.no \
--to=sb@metis.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).