notmuch/lib, branch debian/0.24_rc0-1

lib: query make exclude handling non-destructive

2017-03-05T00:47:25Z

We filter added exclude at add time, rather than modifying the query by count search. As noted in the comments, there are several ignored conditions here.

lib: centralize query parsing, store results.

2017-03-05T00:47:25Z

The main goal is to prepare the way for non-destructive (or at least less destructive) exclude tag handling. It does this by having a pre-parsed query available for further processing. This also allows us to provide slightly more precise error messages.

lib: use delete[] to free buffer allocated using new[]

2017-03-05T00:42:39Z

Fix warning caught by clang: lib/regexp-fields.cc:41:2: warning: 'delete' applied to a pointer that was allocated with 'new[]'; did you mean 'delete[]'? [-Wmismatched-new-delete] delete buffer; ^ [] lib/regexp-fields.cc:37:17: note: allocated with 'new[]' here char *buffer = new char[len]; ^

lib: add mid: as a synonym for id:

2017-03-03T21:46:48Z

mid: is the url scheme suggested by URL 2392. We also plan to introduce more flexible searches for mid: than are possible with id: (in order not to break assumptions about the special behaviour of id:, e.g. identifying at most one message).

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.

lib: create field processors from prefix table

2017-03-03T11:15:13Z

This is a bit more code than hardcoding the two existing field processors, but it should make it easy to add more.

lib/message.cc: use view number to invalidate cached metadata

2017-02-26T01:15:38Z

Currently the view number is incremented by notmuch_database_reopen

lib: handle DatabaseModifiedError in _n_message_ensure_metadata

2017-02-26T01:13:50Z

The retries are hardcoded to a small number, and error handling aborts than propagating errors from notmuch_database_reopen. These are both somewhat justified by the assumption that most things that can go wrong in Xapian::Database::reopen are rare and fatal. Here's the brief discussion with Xapian upstream: 24-02-2017 08:12:57 < bremner> any intuition about how likely Xapian::Database::reopen is to fail? I'm catching a DatabaseModifiedError somewhere where handling any further errors is tricky, and wondering about treating a failed reopen as as "the impossible happened, stopping" 24-02-2017 16:22:34 < olly> bremner: there should not be much scope for failure - stuff like out of memory or disk errors, which are probably a good enough excuse to stop

lib: add _notmuch_database_reopen

2017-02-26T01:09:17Z

The main expected use is to recover from a Xapian::DatabaseChanged exception.

Merge branch 'release'

2017-02-23T13:08:15Z

Merge in g_hash_table read-after-free fix