notmuch/lib/regexp-fields.cc, branch 0.29_rc0

lib: use phrase search for anything not ending in '*'

2019-03-28T17:34:37Z

Anything that does not look like a wildcard should be safe to quote. This should fix the problem searching for xapian keywords.

Prepend regerror() messages with "regexp error: "

2019-03-12T01:24:55Z

The exact error messages returned by regerror() aren't standardized; relying on them isn't portable. Thus, add a a prefix to make clear that the subsequent message is a regexp parsing error, and only look for this prefix in the test suite, ignoring the rest of the message.

lib: Add regexp expansion for for tags and paths

2017-05-09T10:44:29Z

From a UI perspective this looks similar to what was already provided for from, subject, and mid, but the implementation is quite different. It uses the database's list of terms to construct a term based query equivalent to the passed regular expression.

lib: Add regexp searching for mid: prefix

2017-05-09T10:44:15Z

The bulk of the change is passing in the field options to the regexp field processor, so that we can properly handle the fallback (non-regexp case).

lib: handle empty string in regexp field processors

2017-03-29T23:44:32Z

The non-field processor behaviour is is convert the corresponding queries into a search for the unprefixed terms. This yields pretty surprising results so I decided to generate a query that would match the terms (i.e. none with that prefix) generated for an empty header.

lib: only trigger phrase processing for regexp fields when needed

2017-03-24T12:24:13Z

The argument is that if the string passed to the field processor has no spaces, then the added quotes won't have any benefit except for disabling wildcards. But disabling wildcards doesn't seem very useful in the normal Xapian query parser, since they're stripped before generating terms anyway. It does mean that the query 'from:"foo*"' will not be precisely equivalent to 'from:foo' as it is for the non field-processor version.

lib: Fix RegexpPostingSource

2017-03-07T23:44:36Z

Remove incorrect skipping to first match from init(), and add explicit skip_to() and check() methods to work around xapian-core bug (the check() method will also improve speed when filtering by one of these).

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: 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.