notmuch/doc/man7, branch 0.24

lib: regexp matching in 'subject' and 'from'

2017-03-03T21:46:48Z

the idea is that you can run % notmuch search subject:// % notmuch search from:// or % notmuch search subject:"your usual phrase search" % notmuch search from:"usual phrase search" This feature is only available with recent Xapian, specifically support for field processors is needed. It should work with bindings, since it extends the query parser. This is easy to extend for other value slots, but currently the only value slots are date, message_id, from, subject, and last_mod. Date is already searchable; message_id is left for a followup commit. This was originally written by Austin Clements, and ported to Xapian field processors (from Austin's custom query parser) by yours truly.

add property: query prefix to search for specific properties

2016-09-21T21:14:25Z

We want to be able to query the properties directly, like: notmuch count property:foo=bar which should return a count of messages where the property with key "foo" has value equal to "bar".

doc: clean up boolean vs. probabilistic prefixes

2016-06-07T11:00:40Z

sphinx-build emits a minor warning: [...]doc/man7/notmuch-search-terms.rst:223: WARNING: Block quote ends without a blank line; unexpected unindent. And the tabular representation of boolean or probabilistic prefixes currently renders like this when i view it in man: ┌───────────────────────────┬────────────────────────────┐ │Boolean │ Probabilistic │ └───────────────────────────┴────────────────────────────┘ │ tag: id: │ from: to: │ │ │ │ │ thread: folder: │ subject: attach‐ │ │ path: │ ment: mimetype: │ └───────────────────────────┴────────────────────────────┘ This isn't just ugly: it's confusing, because it seems to imply that some of the prefixes in the left-hand column are somehow related to specific other prefixes in the right-hand column. The Definition List representation introduced by this patch should be simpler for readers to understand, and doesn't have the warning.

lib: add support for named queries

2016-05-25T10:40:44Z

This relies on the optional presense of xapian field processors, and the library config API.

lib: optionally support single argument date: queries

2016-05-08T11:17:07Z

This relies on the FieldProcessor API, which is only present in xapian >= 1.3.

man: clarify the parameters for lastmod: range query

2015-10-21T12:13:33Z

and for the lastmod: prefix right below the date: prefix description give the impression one could use last modified dates to lastmod: which is not at all the case. Use .. instead.

lib: add support for date:..! to mean date:..

2015-09-26T00:55:24Z

It doesn't seem likely we can support simple date: expanding to date:.. any time soon. (This can be done with a future version of Xapian, or with a custom query query parser.) In the mean time, provide shorthand date:..! to mean the same. This is useful, as the expansion takes place before interpetation, and we can use, for example, date:yesterday..! to match from beginning of yesterday to end of yesterday. Idea from Mark Walters .

lib: Add "lastmod:" queries for filtering by last modification

2015-08-14T16:23:49Z

The implementation is essentially the same as the date range search prior to Jani's fancy date parser.

doc: update list of prefixes

2015-02-24T07:29:01Z

'attachement' missed a colon, and 'mimetype' was not added to this table at all.

doc: typo fix for prefix discussion.

2015-02-24T07:29:01Z