From: Austin Clements <amdragon@MIT.EDU>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [Emacs] Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages
Date: Wed, 25 Jan 2012 20:19:03 -0500 [thread overview]
Message-ID: <20120126011903.GA1176@mit.edu> (raw)
In-Reply-To: <20120126004024.GA13704@shi.workgroup>
Quoth Gregor Zattler on Jan 26 at 1:40 am:
> [sorry for the long and meandering explanation, I do not know how
> to express the issue more concise]
>
> Dear notmuch developers,
>
> may someone please enlighten me regarding this behaviour:
>
> I experienced a situation where the Emacs interface shows three
> (3) different threads in one notmuch show buffer. I thought it
> should show only one. Perhaps this is the result of notmuch show
> showing messages which do not match the search pattern and do not
> belong to one thread which contains messages which do so.[1]
It's always possible that this is a bug, but one potential legitimate
cause comes to mind. If *any* of the messages in each of the
apparently unrelated threads contain a message ID of any of the
messages in the original thread (or one of the other unrelated
threads) in their References or In-reply-to headers, notmuch will
merge the threads and cause the exact behavior you're seeing.
One very common cause of this is someone using "reply" to get an
initial set of recipients, but then replacing the entire message and
subject (presumably without realizing that the mail is still tracking
what it was a reply to). This can also happen if someone
intentionally replies to multiple messages (though few mail clients
support this), or if there was a message ID collision.
next prev parent reply other threads:[~2012-01-26 1:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 0:40 [Emacs] Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages Gregor Zattler
2012-01-26 1:19 ` Austin Clements [this message]
2012-01-26 2:31 ` Jameson Graef Rollins
2012-01-26 12:44 ` Gregor Zattler
2012-01-26 13:16 ` Jani Nikula
2012-01-29 23:36 ` Gregor Zattler
2012-01-26 13:32 ` Pieter Praet
2012-01-29 23:42 ` Gregor Zattler
2012-01-30 7:06 ` Pieter Praet
2012-01-30 19:04 ` Gregor Zattler
2012-01-30 21:27 ` Mark Walters
2012-01-30 22:34 ` Gregor Zattler
2012-01-31 1:18 ` Mark Walters
2012-01-31 16:31 ` Jameson Graef Rollins
2014-01-24 13:35 ` David Bremner
2014-01-26 21:26 ` Gregor Zattler
2014-01-26 23:43 ` David Bremner
2014-01-27 1:48 ` Gregor Zattler
2014-02-17 0:16 ` David Bremner
2014-01-27 17:07 ` Eric
2017-07-09 17:10 ` David Bremner
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=20120126011903.GA1176@mit.edu \
--to=amdragon@mit.edu \
--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).