notmuch/lib/message.cc, branch debian/0.29-2

indexing: record protected subject when indexing cleartext

2019-05-29T11:14:44Z

When indexing the cleartext of an encrypted message, record any protected subject in the database, which should make it findable and visible in search. Signed-off-by: Daniel Kahn Gillmor

lib: support user prefix names in term generation

2019-05-25T10:17:27Z

This should not change the indexing process yet as nothing calls _notmuch_message_gen_terms with a user prefix name. On the other hand, it should not break anything either. _notmuch_database_prefix does a linear walk of the list of (built-in) prefixes, followed by a logarithmic time search of the list of user prefixes. The latter is probably not really noticable.

n_m_remove_indexed_terms: reduce number of Xapian API calls.

2019-05-23T11:00:56Z

Previously this functioned scanned every term attached to a given Xapian document. It turns out we know how to read only the terms we need to preserve (and we might have already done so). This commit replaces many calls to Xapian::Document::remove_term with one call to ::clear_terms, and a (typically much smaller) number of calls to ::add_term. Roughly speaking this is based on the assumption that most messages have more text than they have tags. According to the performance test suite, this yields a roughly 40% speedup on "notmuch reindex '*'"

lib: add 'body:' field, stop indexing headers twice.

2019-04-17T11:48:16Z

The new `body:` field (in Xapian terms) or prefix (in slightly sloppier notmuch) terms allows matching terms that occur only in the body. Unprefixed query terms should continue to match anywhere (header or body) in the message. This follows a suggestion of Olly Betts to use the facility (since Xapian 1.0.4) to add the same field with multiple prefixes. The double indexing of previous versions is thus replaced with a query time expension of unprefixed query terms to the various prefixed equivalent. Reindexing will be needed for 'body:' searches to work correctly; otherwise they will also match messages where the term occur in headers (demonstrated by the new tests in T530-upgrade.sh)

lib: calculate message depth in thread

2018-09-06T11:07:13Z

This will be used in reparenting messages without useful in-reply-to, but with useful references

lib: read reference terms into message struct.

2018-09-06T11:07:12Z

The plan is to use these in resolving threads.

lib/thread: sort sibling messages by date

2018-09-06T11:07:12Z

For non-root messages, this should not should anything currently, as the messages are already added in date order. In the future we will add some non-root messages in a second pass out of order and the sorting will be useful. It does fix the order of multiple root-messages (although it is overkill for that).

lib: make notmuch_message_get_database() take a const notmuch_message_t*

2018-05-26T14:32:01Z

This is technically an API change, but it is not an ABI change, and it's merely a statement that limits what the library can do. This is in parallel to notmuch_query_get_database(), which also takes a const pointer.

lib: expose notmuch_message_get_database()

2018-05-26T14:30:32Z

We've had _notmuch_message_database() internally for a while, and it's useful. It turns out to be useful on the other side of the library interface as well (i'll use it later in this series for "notmuch show"), so we expose it publicly now.

lib: define specialized get_thread_id for use in thread subquery

2018-05-07T11:42:53Z

The observation is that we are only using the messages to get there thread_id, which is kindof a pessimal access pattern for the current notmuch_message_get_thread_id