From: Carl Worth <cworth@cworth.org>
To: David Bremner <david@tethera.net>,
Adam Washington <rprospero@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: Possible bug with named queries
Date: Wed, 13 Dec 2017 15:09:23 -0800 [thread overview]
Message-ID: <87k1xqcjj0.fsf@wondoo.home.cworth.org> (raw)
In-Reply-To: <87k1xq37gr.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Wed, Dec 13 2017, David Bremner wrote:
> 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.
Really? We're deprecating the ability to just edit the configuration
file by hand? That's unfortunate.
> There are technical reasons for certain items being in
> the database, and that's likely to continue.
I won't dispute the technical reasons, (I'm out of the loop on that).
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?
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.
-Carl
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-12-13 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:23 Possible bug with named queries Adam Washington
2017-12-13 16:42 ` David Bremner
2017-12-13 23:09 ` Carl Worth [this message]
2017-12-13 23:47 ` config file vs. config in the database [was: Re: Possible bug with named queries] Daniel Kahn Gillmor
2017-12-14 0:10 ` Possible bug with named queries David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1xqcjj0.fsf@wondoo.home.cworth.org \
--to=cworth@cworth.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=rprospero@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).