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 9BB326DE0ACB for ; Fri, 20 Oct 2017 03:35:08 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 y-FCEiQ-GEOE for ; Fri, 20 Oct 2017 03:35:07 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 420326DE0A9A for ; Fri, 20 Oct 2017 03:35:07 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1e5Ua3-0005wX-C4; Fri, 20 Oct 2017 06:31:07 -0400 Received: (nullmailer pid 21816 invoked by uid 1000); Fri, 20 Oct 2017 10:35:02 -0000 From: David Bremner To: Mark Walters , Jani Nikula , notmuch@notmuchmail.org Subject: Re: [PATCH] lib: add support for thread: queries In-Reply-To: <8760ba5der.fsf@qmul.ac.uk> References: <20171016190754.22581-1-jani@nikula.org> <8760ba5der.fsf@qmul.ac.uk> Date: Fri, 20 Oct 2017 07:35:02 -0300 Message-ID: <87376ehzu1.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Fri, 20 Oct 2017 10:35:08 -0000 Mark Walters writes: > Hi > > On Mon, 16 Oct 2017, Jani Nikula wrote: >> Add support for querying threads using message-ids in addition to >> thread-ids. The main benefit is that thread queries via message-ids >> are portable across databases, re-indexing, and thread joining, while >> thread ids can be somewhat transient. A thread: query can >> be shared between notmuch users, while a thread: query may >> cease to work after the regular delivery of a message that joins >> threads. > > I like the idea. > > Just one thought -- is any form of recursion allowed in this sort of > operator so could we have thread:'some query' which would expand to all > threads matching the query? I am guessing this may not be possible now > but would it be worth requiring the thread form to be > thread:id: rather than thread:? In id:20170820213240.20526-1-david@tethera.net I used thread:{} to introduce an arbitrary query. That syntax seems ok to me, and doesn't conflict with Jani's patch. I think Jani mentioned at the time that thread:{id:foo} was a too much typing. d