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 33C446DE0C1B for ; Wed, 13 Dec 2017 08:42:32 -0800 (PST) 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 L7qQRCTlJv6m for ; Wed, 13 Dec 2017 08:42:31 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 39A0B6DE0962 for ; Wed, 13 Dec 2017 08:42:31 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1ePA73-0008El-UW; Wed, 13 Dec 2017 11:42:29 -0500 Received: (nullmailer pid 30661 invoked by uid 1000); Wed, 13 Dec 2017 16:42:28 -0000 From: David Bremner To: Adam Washington , notmuch@notmuchmail.org Subject: Re: Possible bug with named queries In-Reply-To: <871sjyiwwx.fsf@stfc.ac.uk> References: <871sjyiwwx.fsf@stfc.ac.uk> Date: Wed, 13 Dec 2017 12:42:28 -0400 Message-ID: <87k1xq37gr.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: Wed, 13 Dec 2017 16:42:32 -0000 Adam Washington writes: > I've either stumbled across a bug in the handling of named queries or > (more likely) a bug in their documentation. I've tried creating some > named queries by adding the following three lines to my > .notmuch-config file. you should use "notmuch config" to add named queries. In the latest version of the docs (will be in the next release), these are noted as STORED IN DATABASE, thanks to some doc cleanup by dkg. In general I'd recommend using using "notmuch config" for all configuration changes, then you don't have to keep track of which ones are stored in .notmuch-config. There are technical reasons for certain items being in the database, and that's likely to continue. d