mirror of
https://github.com/djcb/mu.git
synced 2024-06-28 07:41:04 +02:00
mu's query parser is the piece of software that turns your queries into something the Xapian database can understand. So, if you query "maildir:/inbox and subject:bla" this must be translated into a Xapian::Query object which will retrieve the sought after messages. Since mu's beginning, almost a decade ago, this parser was based on Xapian's default Xapian::QueryParser. It works okay, but wasn't really designed for the mu use-case, and had a bit of trouble with anything that's not A..Z (think: spaces, special characters, unicode etc.). Over the years, mu added quite a bit of pre-processing trickery to deal with that. Still, there were corner cases and bugs that were practically unfixable. The solution to all of this is to have a custom query processor that replaces Xapian's, and write it from the ground up to deal with the special characters etc. I wrote one, as part of my "future, post-1.0 mu" reseach project, and I have now backported it to the mu 0.9.19. From a technical perspective, this is a major cleanup, and allows us to get rid of much of the fragile preprocessing both for indexing and querying. From and end-user perspective this (hopefully) means that many of the little parsing issues are gone, and it opens the way for some new features. From an end-user perspective: - better support for special characters. - regexp search! yes, you can now search for regular expressions, e.g. subject:/h.ll?o/ will find subjects with hallo, hello, halo, philosophy, ... As you can imagine, this can be a _heavy_ operation on the database, and might take quite a bit longer than a normal query; but it can be quite useful. |
||
---|---|---|
.. | ||
data.hh | ||
dummy-processor.hh | ||
Makefile.am | ||
parse.cc | ||
parser.cc | ||
parser.hh | ||
proc-iface.hh | ||
test-parser.cc | ||
test-tokenizer.cc | ||
test-utils.cc | ||
tokenize.cc | ||
tokenizer.cc | ||
tokenizer.hh | ||
tree.hh | ||
utils.cc | ||
utils.hh | ||
xapian.cc | ||
xapian.hh |