From: David Bremner <david@tethera.net>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
notmuch@notmuchmail.org
Subject: Re: 'notmuch search thread:<>' lists multiple threads
Date: Sat, 21 Apr 2018 21:45:49 -0300 [thread overview]
Message-ID: <87r2n8m5ky.fsf@tethera.net> (raw)
In-Reply-To: <1524045467.a0aq8zermb.naveen@linux.ibm.com>
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:
> In my case, I seem to be having the In-Reply-To headers. I end up with
> two files per message: one from my inbox and one from the gmane archive
> that I pull in. All the messages from the gmane archive seem to have a
> re-written 'In-Reply-To' header, but 'Message-Id' and 'References' are
> the same.
That sounds like essentially the same issue, due to the fact that
notmuch prefers In-Reply-To when choosing a parent for a message.
Currently the database is correct (or at least one not-crazy definition
of correct): all of the reference and in-reply-to terms are attached to
the message document in the database. On the other hand, the in memory
data structures currently assume that In-reply-to is a unique value
(with ties broken at indexing time).
It might be that the solution is to read a list of in-reply-to values
and use all of them in threading. At a quick glance, that looks doable;
I'm just not sure about unintended consequences.
d
next prev parent reply other threads:[~2018-04-22 0:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 9:46 'notmuch search thread:<>' lists multiple threads Naveen N. Rao
2018-04-06 10:23 ` Naveen N. Rao
2018-04-08 3:04 ` David Bremner
2018-04-09 11:54 ` David Bremner
2018-04-10 1:45 ` [PATCH] devel: add new tool to draw thread structure David Bremner
2018-10-08 3:30 ` Daniel Kahn Gillmor
2018-04-18 10:18 ` 'notmuch search thread:<>' lists multiple threads Naveen N. Rao
2018-04-22 0:45 ` David Bremner [this message]
2018-06-28 10:36 ` Naveen N. Rao
2018-06-30 13:42 ` David Bremner
2018-08-30 12:52 ` David Bremner
2018-09-06 10:50 ` Naveen N. Rao
2019-06-27 14:45 ` Naveen N. Rao
2019-06-27 14:53 ` Naveen N. Rao
2021-12-23 18:00 ` David Bremner
2022-01-14 11:26 ` Naveen N. Rao
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2n8m5ky.fsf@tethera.net \
--to=david@tethera.net \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).