config file vs. config in the database [was: Re: Possible bug with named queries]

2017-12-13 Thread Daniel Kahn Gillmor
Hi Carl, all-- thanks for raising this subject! I've taken this opportunity to write down a bit more justification for why i lean in the direction that Bremner describes, but would be happy to be argued out of it. On Wed 2017-12-13 15:09:23 -0800, Carl Worth wrote: > Really? We're deprecating

Re: Possible bug with named queries

2017-12-13 Thread 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

Re: Possible bug with named queries

2017-12-13 Thread Carl Worth
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

Re: Possible bug with named queries

2017-12-13 Thread David Bremner
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

Possible bug with named queries

2017-12-13 Thread Adam Washington
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. [query] sasview=from:sasview.org or (from:github subject:sasview) or