From: Adam Washington <rprospero@gmail.com>
To: notmuch@notmuchmail.org
Subject: Possible bug with named queries
Date: Wed, 13 Dec 2017 13:23:42 +0000 [thread overview]
Message-ID: <871sjyiwwx.fsf@stfc.ac.uk> (raw)
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 (from:github subject:sasmodels)
mantid=from:mantidproject.org
If I run `notmuch config list`, the following lines are amongst the output
crypto.gpg_path=gpg
query.sasview=from:sasview.org or (from:github subject:sasview) or (from:github subject:sasmodels)
query.mantid=from:mantidproject.org
built_with.compact=true
However, the queries do not seem to work.
$ notmuch count from:mantidproject.org
7
$ notmuch count query:mantid
0
Also, while the output from `notmuch config list` showed both queries,
trying to view them gives no result.
$ notmuch config get mantid
$
I'm guessing that the queries aren't configured properly, but I can't
seem to find any documentation that indicates that I'm doing something
wrong. The man page for notmuch-config states that the explanation
for named queries is in notmuch-search-terms, which, in turn, points
back to notmuch-config.
Is this a bug or have I declared my queries incorrectly?
next reply other threads:[~2017-12-13 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 13:23 Adam Washington [this message]
2017-12-13 16:42 ` Possible bug with named queries David Bremner
2017-12-13 23:09 ` Carl Worth
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=871sjyiwwx.fsf@stfc.ac.uk \
--to=rprospero@gmail.com \
--cc=notmuch@notmuchmail.org \
/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).