Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 35796431FC2 for ; Fri, 25 Jul 2014 03:08:25 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ze+OuWUI+aR for ; Fri, 25 Jul 2014 03:08:19 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id AB257431FAF for ; Fri, 25 Jul 2014 03:08:19 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1XAcQ4-0002QH-VR; Fri, 25 Jul 2014 07:08:08 -0300 Received: (nullmailer pid 8147 invoked by uid 1000); Fri, 25 Jul 2014 10:08:01 -0000 From: David Bremner To: Stefano Zacchiroli , 755246@bugs.debian.org Subject: Re: Bug#755246: notmuch-mutt: search that returns whole threads In-Reply-To: <20140722114049.GB30408@upsilon.cc> References: <20140719025928.GA25672@siren> <20140719173500.GA9660@upsilon.cc> <20140719210111.GA28049@siren> <20140719211106.GA26819@upsilon.cc> <874my9elz7.fsf@maritornes.cs.unb.ca> <20140722114049.GB30408@upsilon.cc> User-Agent: Notmuch/0.18.1+45~gf47eeac (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Fri, 25 Jul 2014 07:08:01 -0300 Message-ID: <8761iln43i.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain Cc: Vagrant Cascadian , Notmuch Mail X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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, 25 Jul 2014 10:08:25 -0000 Stefano Zacchiroli writes: > > In fact, I was hoping in some sort of meta-syntax, to piggyback on. For > instance, if "field:value" is something that is always threated > specially by notmuch, we can use something like "notmuch:threads" (vs, > say, "notmuch:nothreads") and strip it before it hits notmuch. > > If you've no objection to this, I can implement something like it. (bringing in the upstream list, as this is really an upstream design issue) Currently any unrecognized field:value will be searched for as a phrase [1], and is equivalent to "field value", field.value, field-value, among others. So as long as notmuch: is not a recognized prefix, your scheme will not block any searches. It doesn't seem especially likely that we'll want to use "notmuch:" as a prefix; of course if you were to choose something with "mutt" in the name that would be more nearly a sure thing. [1]: http://xapian.org/docs/queryparser.html