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 F2A536DE0C51 for ; Wed, 13 Dec 2017 16:10:57 -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 Re0lE2weX9VV for ; Wed, 13 Dec 2017 16:10:57 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id E50E76DE0C45 for ; Wed, 13 Dec 2017 16:10:56 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1ePH6x-0000fc-Cs; Wed, 13 Dec 2017 19:10:51 -0500 Received: (nullmailer pid 12059 invoked by uid 1000); Thu, 14 Dec 2017 00:10:50 -0000 From: David Bremner To: Carl Worth , notmuch@notmuchmail.org Subject: Re: Possible bug with named queries In-Reply-To: <87k1xqcjj0.fsf@wondoo.home.cworth.org> References: <871sjyiwwx.fsf@stfc.ac.uk> <87k1xq37gr.fsf@tethera.net> <87k1xqcjj0.fsf@wondoo.home.cworth.org> Date: Wed, 13 Dec 2017 20:10:50 -0400 Message-ID: <87wp1q1851.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: Thu, 14 Dec 2017 00:10:58 -0000 Carl Worth writes: > But if running "notmuch config" to add a saved search stores some > necessary data in the database, couldn't the same code be invoked when > loading the configuration file and noticing a new saved search there in > the file? It could (with some complications, e.g. for users of libnotmuch). But the version in the database can change via the libnotmuch API, which presumably should be written to the config file. I'm not sure how that would all work. > We've gone out of our way to make the configuration file as useful as > possible, (such as by maintaining comments in the file even when using a > tool such as "notmuch config" to edit it). Let's please not throw out > all the benefits by just saying that manually editing the configuration > file is unreliable and people shouldn't do it. Well, it's reliable if people read the (new) documentation carefully. But obviously it's a bit surprising that some things are just ignored in .notmuch-config. It should be possible to report warnings for those items. IIRC, one thing we (collectively) discussed and rejected is having a seperate command to manipulate database resident configuration information. That could still be done. d