Re: Possible bug with named queries

Subject: Re: Possible bug with named queries

Date: Wed, 13 Dec 2017 20:10:50 -0400

To: Carl Worth,


From: David Bremner

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.

notmuch mailing list