unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
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: Mon, 27 Jan 2014 02:48:12 +0100	[thread overview]
Message-ID: <20140127014812.GE10844@boo.workgroup> (raw)
In-Reply-To: <87r47ul364.fsf@zancas.localnet>

Hi David,
* David Bremner <david@tethera.net> [26. Jan. 2014]:
> Gregor Zattler <telegraph@gmx.net> writes:
> 
>> Today I produced another mbox with the very same command but with
>> a now larger email corpus freshly indexed with a fresh notmuch.
>> The mbox contains (according to mutt) 507 messages in 34 threads.
>> One of them is the thread I searched for.
>>
>> I grepped for the 7 subjects within the 34 subjects and only 5
>> showed up.
> 
> I don't know what you mean here. Grepped where? in the raw messages?

With mutt I had a view at the collapsed 7 respective 34 threads.
One then sees the very first E-Mails of a thread and among other
information their subjects.
Via editing I produced two lists with subjects and then searched
each of the 7 in the list with the 34.

>> If somebody want's to dig into this: I can provide the two
>> mboxes. 
>>
>> Disclaimer: Many of the emails which arrived before the problem
>> report are not the exact same than then, because since the I
>> mangled them with a script.  This should have not changed the
>> threading but I cannot be 100% sure.  But if it's important for
>> further investigation I'm probably able to reproduce the status
>> quo of the email corpus then from my backups.
> 
> If it's currently not working then I guess your current corpus should be
> fine. It would probably help to restate what exactly is wrong. There was
> a lot of discussion, and the concrete problem I saw identified (in
> id:874nvcekjk.fsf@qmul.ac.uk ) was that certain malformed In-reply-to
> headers were causing unrelated threads to merge.

Yes.  I understood the commit message of the commit you
referenced in the email I answered to, that now notmuch uses
 Reference: headers to do the threading.  I had a quick view at
the References header in the mbox file and none looked
suspicious.

Ciao, Gregor
-- 
 -... --- .-. . -.. ..--.. ...-.-

  reply	other threads:[~2014-01-27  1:54 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
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 [this message]
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=20140127014812.GE10844@boo.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).