mirror of
https://github.com/djcb/mu.git
synced 2024-06-27 07:35:16 +02:00
26b3110b8f
Previously, we would conduct regular expression searches by enumerating all values of a given term, manually regex-matching each one against our search regular expression, remember all the term values that matched our regular expression, then do a big Xapian OR-query that matched any of those term values. In constructing this OR-query, however, we would split each term value on space and add a separate Xapian phrase search term for each resulting word. This approach worked fine most of the time, beacuse when we index a term, we index both each word in a term and the whole term by itself. This word splitting produced false negatives in some matches, however, because Xapian and the Mu-level word splitting code do word splitting slightly differently and apply different transformations to the text while splitting. (For example, Xapian transforms fancy Unicode apostrophes to ASCII apostrophes.) This patch avoids the problem by not word splitting when constructing the big Xapian OR-query for finding the results of regular expression matching. |
||
|---|---|---|
| .. | ||
| index | ||
| message | ||
| tests | ||
| thirdparty | ||
| utils | ||
| doxyfile.in | ||
| meson.build | ||
| mu-bookmarks.cc | ||
| mu-bookmarks.hh | ||
| mu-contacts-cache.cc | ||
| mu-contacts-cache.hh | ||
| mu-maildir.cc | ||
| mu-maildir.hh | ||
| mu-parser.cc | ||
| mu-parser.hh | ||
| mu-query-match-deciders.cc | ||
| mu-query-match-deciders.hh | ||
| mu-query-results.hh | ||
| mu-query-threads.cc | ||
| mu-query-threads.hh | ||
| mu-query.cc | ||
| mu-query.hh | ||
| mu-script.cc | ||
| mu-script.hh | ||
| mu-server.cc | ||
| mu-server.hh | ||
| mu-store.cc | ||
| mu-store.hh | ||
| mu-tokenizer.cc | ||
| mu-tokenizer.hh | ||
| mu-tree.hh | ||
| mu-xapian.cc | ||
| mu-xapian.hh | ||
| tokenize.cc | ||