notmuch/test/T650-regexp-query.sh, branch releasethread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=release2022-03-19T10:27:29Zlib: do not phrase parse prefixed bracketed subexpressions2022-03-19T10:27:29ZDavid Bremnerdavid@tethera.net2022-02-25T02:41:03Zurn:sha1:8ed6a172b35708428f84f30af44fa81c12852e43
Since Xapian does not preserve quotes when passing the subquery to a
field processor, we have to make a guess as to what the user
intended. Here the added assumption is that a string surrounded by
parens is not intended to be a phrase.
test: known broken tests for bracketed terms in subject2022-03-19T10:27:00ZDavid Bremnerdavid@tethera.net2022-02-25T02:41:02Zurn:sha1:c9ed87f39f54b83ecafc719e848909da6074075f
The heuristics in the field processor currently incorrectly trigger
phrase parsing.
build: drop support for xapian versions less than 1.42020-04-24T00:28:45ZTomi Ollilatomi.ollila@iki.fi2020-04-21T21:07:29Zurn:sha1:00cdfe10717020423870fdaf56e973db9aba9f5a
Xapian 1.4 is over 3 years old now (1.4.0 released 2016-06-24),
and 1.2 has been deprecated in Notmuch version 0.27 (2018-06-13).
Xapian 1.4 supports compaction, field processors and retry locking;
conditionals checking compaction and field processors were removed
but user may want to disable retry locking at configure time so it
is kept.
tests: remove some redundant pre-cleanup of the corpus MAIL_DIR2019-05-07T09:52:35ZJameson Graef Rollinsjrollins@finestructure.net2019-05-04T20:57:45Zurn:sha1:7f7af27bd8320fd7a7e7ab50bf0c206da3775635
add_email_corpus itself does an rm -rf $MAIL_DIR, so these are not necessary.
lib: use phrase search for anything not ending in '*'2019-03-28T17:34:37ZDavid Bremnerdavid@tethera.net2018-09-30T16:27:55Zurn:sha1:d25dcc589ce4c1a87d698c6aef1ce3e38e4a50bb
Anything that does not look like a wildcard should be safe to
quote. This should fix the problem searching for xapian keywords.
test: add two known broken tests searching for xapian keywords2019-03-28T17:32:11ZDavid Bremnerdavid@tethera.net2018-09-30T16:27:54Zurn:sha1:168211c5632189c53415d25530b759ad3678c92c
Thanks to plujon for pointing out this problem on IRC. The underlying
issue is that the quotes are stripped before the field processors get
the query string, and the heuristic for putting them back is not quite
right.
Prepend regerror() messages with "regexp error: "2019-03-12T01:24:55ZLuis Resselaranea@aixah.de2019-03-11T17:14:49Zurn:sha1:9f7e851263b96acacc9ea542e9f5d837563fea05
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.
test: use $(dirname "$0") for sourcing test-lib.sh2017-10-20T22:52:49ZJani Nikulajani@nikula.org2017-09-25T20:38:19Zurn:sha1:a863de1e43ee34f6f5794a2759fdceb287e851aa
Don't assume the tests are always run from within the source tree.
cli/search: print total number of files matched in summary output.2017-08-02T01:17:47ZDavid Bremnerdavid@tethera.net2017-06-04T12:32:32Zurn:sha1:ed4a9082c02d0a73f5f7d07f90a7daf65bde0aaa
The structured output formats already have all of the filenames. This
is an easy bit of UI change to make the multiple files visible.
lib: Add regexp expansion for for tags and paths2017-05-09T10:44:29ZDavid Bremnerdavid@tethera.net2017-03-08T02:32:26Zurn:sha1:11d47950c18f2d19718e35b7264dabf2ff2fd621
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.