From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id CD3116DE0BA2 for ; Sat, 16 Nov 2019 07:31:25 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.06 X-Spam-Level: X-Spam-Status: No, score=-0.06 tagged_above=-999 required=5 tests=[AWL=-0.059, SPF_PASS=-0.001] 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 DfRnAfEp6eSN for ; Sat, 16 Nov 2019 07:31:24 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 8D6A76DE0B72 for ; Sat, 16 Nov 2019 07:31:24 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1iW02g-00070U-3b; Sat, 16 Nov 2019 10:31:18 -0500 Received: (nullmailer pid 2870 invoked by uid 1000); Sat, 16 Nov 2019 15:31:16 -0000 From: David Bremner To: Jameson Graef Rollins , Daniel Kahn Gillmor , Notmuch Mail Subject: Re: can a notmuch query filter the output based on the size of a thread? In-Reply-To: <87eeyeut7o.fsf@caltech.edu> References: <871ruetona.fsf@fifthhorseman.net> <87y2wmuww0.fsf@caltech.edu> <87pnhys1dh.fsf@fifthhorseman.net> <87eeyeut7o.fsf@caltech.edu> Date: Sat, 16 Nov 2019 10:31:16 -0500 Message-ID: <87o8xbu9bv.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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, 16 Nov 2019 15:31:25 -0000 Jameson Graef Rollins writes: > I have never personally had the need to search based on numbers of > messages, but I have definitely thought that it would be good if > searches worked over entire threads instead of just messages. I would > much prefer if a search for "foo AND bar" would turn up a thread where > "foo" was mentioned in one message in the thread and "bar" was mentioned > in another. I think that would be very useful. You can use thread:{foo AND bar} for that (with appropriate quoting). There is a noticable performance penalty. d