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 779D86DE0EC5 for ; Sun, 3 Mar 2019 17:54:48 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.01 X-Spam-Level: X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 BPjbRe2-i4K3 for ; Sun, 3 Mar 2019 17:54:47 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 51D4A6DE0C3D for ; Sun, 3 Mar 2019 17:54:47 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1h0coW-0002Su-IJ for notmuch@notmuchmail.org; Sun, 03 Mar 2019 20:54:44 -0500 Received: (nullmailer pid 7439 invoked by uid 1000); Mon, 04 Mar 2019 01:54:42 -0000 From: David Bremner To: notmuch@notmuchmail.org Subject: Re: WIP2: index user headers In-Reply-To: <87fts4xazk.fsf@tethera.net> References: <20190302154133.25642-1-david@tethera.net> <87fts4xazk.fsf@tethera.net> Date: Sun, 03 Mar 2019 21:54:42 -0400 Message-ID: <8736o3xv31.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: Mon, 04 Mar 2019 01:54:48 -0000 David Bremner writes: > I had another thought about user prefixes. I wonder if they should all > be forcibly prefixed with something that prevents collisions, to prevent > later pain if we add an "official" prefix with the same name. A quick > tests suggest it would work to use something like _ > > so > > notmuch search --output=files _list:notmuch > > works. It's a bit ugly, I'll have to play with other options; the main > question is whether we think prefixing is needed / worth-it. I played with the query parser a bit, and the only idea I found so far is to reserve prefixes starting with lower case ASCII for notmuch, and allow users to use anything else. d