Return-Path: 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 BA82F6DE00CB for ; Sat, 19 Sep 2015 09:04:10 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.113 X-Spam-Level: X-Spam-Status: No, score=0.113 tagged_above=-999 required=5 tests=[AWL=0.113] 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 dijjLOwqQwln for ; Sat, 19 Sep 2015 09:04:09 -0700 (PDT) Received: from gitolite.debian.net (gitolite.debian.net [87.98.215.224]) by arlo.cworth.org (Postfix) with ESMTPS id BD59C6DE009A for ; Sat, 19 Sep 2015 09:04:08 -0700 (PDT) Received: from remotemail by gitolite.debian.net with local (Exim 4.80) (envelope-from ) id 1ZdKb3-0002oL-Bw; Sat, 19 Sep 2015 16:02:41 +0000 Received: (nullmailer pid 26004 invoked by uid 1000); Sat, 19 Sep 2015 16:02:22 -0000 From: David Bremner To: Xu Wang , notmuch@notmuchmail.org Subject: Re: Possible some threads are not complete due to bug? In-Reply-To: References: User-Agent: Notmuch/0.20.2+73~gd432116 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sat, 19 Sep 2015 13:02:22 -0300 Message-ID: <87fv2a4ctt.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2015 16:04:10 -0000 Xu Wang 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: > 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? > Indeed, that mail belongs to a different thread ID. How can you tell that the mail belongs to a different thread? Isn't that what your first command tells you? d