From: Gregor Zattler <telegraph@gmx.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: Bug?: notmuch-search-show-thread shows several threads; only one containing matching messages
Date: Thu, 26 Jan 2012 13:44:50 +0100 [thread overview]
Message-ID: <20120126124450.GB30209@shi.workgroup> (raw)
In-Reply-To: <8762fzry7k.fsf@servo.finestructure.net>
Hi Jamie, Austin,
* Jameson Graef Rollins <jrollins@finestructure.net> [25. Jan. 2012]:
> On Wed, 25 Jan 2012 20:19:03 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
>> 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.
>
> This is a very common occurrence for me as well. I would put money down
> that this is what you're seeing.
I thought about this too and this is why I checked for any
occurrence of Message-IDs in the other emails:
|> I isolated the thread I was interested in,
|> extracted the message ids of its messages and greped the rest of
|> the messages for this message ids: no matches.[2] Therefore no of
|> the rests messages are part of the thread I was interested in
perhaps there was a logic error in how I did this:
|> [2] grep -I "^Message-Id:" /tmp/thread-I-m-interested-in.mbox |sed -e "s/Message-Id: <//I" -e "s/>$//" >really.mid
|> grep -I -F really.mid rest.mbox
|> --> no match
/tmp/thread-I-m-interested-in.mbox is a mbox with messages
I'minterested in, the "real" ones. really.mid is a list of
Message-IDs of these "real" emails. rest.mbox is a mbox with the
other emails, Emacs showed in his notmuch show buffer but are
other threads.
Since there is no match I concluded, the threads are not linked.
Perhaps I made a mistake. I'l retest it and report again. But
right now I don't have the time to do this.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2012-01-26 12:45 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
2012-01-26 2:31 ` Jameson Graef Rollins
2012-01-26 12:44 ` Gregor Zattler [this message]
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=20120126124450.GB30209@shi.workgroup \
--to=telegraph@gmx.net \
--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).