Return-Path: <xuwang762@gmail.com>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
 by arlo.cworth.org (Postfix) with ESMTP id A42576DE1B2E
 for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:34:01 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: -0.203
X-Spam-Level: 
X-Spam-Status: No, score=-0.203 tagged_above=-999 required=5
 tests=[AWL=-0.377, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,
 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,
 RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_SBL=0.644,
 URIBL_SBL_A=0.1] autolearn=disabled
Received: from arlo.cworth.org ([127.0.0.1])
 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 8m4wpxN10yDz for <notmuch@notmuchmail.org>;
 Sun, 20 Sep 2015 07:33:59 -0700 (PDT)
Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com
 [209.85.214.180])
 by arlo.cworth.org (Postfix) with ESMTPS id 3DADC6DE1B2C
 for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:33:59 -0700 (PDT)
Received: by obbda8 with SMTP id da8so66829142obb.1
 for <notmuch@notmuchmail.org>; Sun, 20 Sep 2015 07:33:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=l0lMVYsW5Fb9WxSpbCuAo3EUAIeIeIGK5faO7IQtE3I=;
 b=z6y/fjxoS45cXI6aLsfLqlZKepUapAYuvk7w+SgO4QcUbwLqPgWIm4z7NazbM2y0av
 amrJuIEVrHyOCqlNqZAkqUUr1no9Hp8oNQuhxmy+7Ka9LgQYC1SI2TPSb3Mc4H7Fu5eu
 75Kzpaw9Q7NMi9fKnrb9CAbGab9IjxWDHCye0e3D5NZqAXg4aXciADvAN8auNLwj+m7E
 7YF7wU4mVQwOm+4mIWekRJ6sxwkqbe/I/gphmbMa47txVP9YjaQ56pl0GgKcboYQY/dM
 8pApEU6VRMxtY1oWZbrkNon2dNk+ZzoykQDS6IMuPZEUnne3dIE30WRTKYT0GZ3nnpst
 fCgw==
MIME-Version: 1.0
X-Received: by 10.182.158.164 with SMTP id wv4mr9403505obb.78.1442759638163;
 Sun, 20 Sep 2015 07:33:58 -0700 (PDT)
Received: by 10.202.212.204 with HTTP; Sun, 20 Sep 2015 07:33:58 -0700 (PDT)
In-Reply-To: <87fv2a4ctt.fsf@zancas.localnet>
References:
 <CAJhTkNh7_hXDLsAGyD7nwkXV4ca6ymkLtFG945USvfqK4ZJEdQ@mail.gmail.com>
 <87fv2a4ctt.fsf@zancas.localnet>
Date: Sun, 20 Sep 2015 10:33:58 -0400
Message-ID:
 <CAJhTkNgBdnm18UXC95ryJk5w7fJpa7-1LvdugV3S29fL4kxxhQ@mail.gmail.com>
Subject: Re: Possible some threads are not complete due to bug?
From: Xu Wang <xuwang762@gmail.com>
To: David Bremner <david@tethera.net>
Content-Type: text/plain; charset=UTF-8
Cc: notmuch@notmuchmail.org
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Use and development of the notmuch mail system."
 <notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Sep 2015 14:34:01 -0000

On Sat, Sep 19, 2015 at 12:02 PM, David Bremner <david@tethera.net> wrote:
> Xu Wang <xuwang762@gmail.com> writes:
>
>> Sometimes I need to do:
>>
>> $ notmuch search --output=threads "id:MYMSGID"
>> thread:000000000000a125
>> $ notmuch search --output=messages "thread:000000000000a125"
>>
>> In theory, this should output the message that responded to message ID
>> "MYMSGID". Sometimes it works. But sometimes it does not work. That
>> is, there exists an email where I am sure (I checked the raw email)
>> that there is a header
>> In-Reply-To: <MYMSGID>
>> but that email does not show when I do the two commands above.
>
> I'm not 100% sure what you mean by "does not show". Do you mean that the
> output from the second command is empty? or does not contain MYMSGID?

That was poor formatting on my part. It only was outputting the id I
put into the first command. So it only showed
id:MYMSGID

>> Indeed, that mail belongs to a different thread ID.
>
> How can you tell that the mail belongs to a different thread?

Because when I do a notmuch search for that message by message ID with
--output=threads, it gives a different thread ID.

> Isn't that what your first command tells you?
Well yes, but I wanted to confirm that that is indeed the reason. I
have heard in someone saying that debugging is process of confirming
things that should be true.

Kind regards,

Xu