notmuch/lib/regexp-fields.cc, branch 0.36thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.362022-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.
lib: drop trailing slash for path and folder searches (infix)2022-01-27T11:48:27ZDavid Bremnerdavid@tethera.net2022-01-21T23:38:51Zurn:sha1:c62c22c9fb222d43d9b9956ce6b6e9985019ea2d
This resolves an old bug reported by David Edmondson in 2014. The fix
is only needed for the "boolean" case, as probabilistic / phrase
searching already ignores punctuation.
This fix is only for the infix (xapian provided) query parser.
[1]: id:cunoasuolcv.fsf@gargravarr.hh.sledj.net
lib: factor out query construction from regexp2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:28Zurn:sha1:5cb452c325e1f69e43dca610f48b9396cba9c039
This will allow re-use of this code outside of the Xapian query parser.
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.
lib: run uncrustify2019-06-14T10:41:27Zuncrustifydavid@tethera.net2019-06-13T10:55:35Zurn:sha1:2b62ca2e3b786beca8d89fa737bda0b49faa638d
This is the result of running
$ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc
in the lib directory
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.
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.
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.
lib: Add regexp searching for mid: prefix2017-05-09T10:44:15ZDavid Bremnerdavid@tethera.net2017-02-15T12:58:28Zurn:sha1:eab365c742f86b52729ec2a5acaba1a798f94661
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 processors2017-03-29T23:44:32ZDavid Bremnerdavid@tethera.net2017-03-24T22:52:51Zurn:sha1:cb84f8487833c19ce13edb769fa6421547077725
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.