notmuch/lib/notmuch-private.h, branch 0.31.3

lib: encapsulate the use of notmuch_database_t field 'mode'

2020-07-28T11:47:58Z

The plan is to change the underlying representation.

lib: rename _n_d_create to _n_d_find_or_create

2020-07-22T22:52:55Z

The error message and name were confusing when called in some "read only" context.

repair: set up codebase for repair functionality

2019-09-01T11:20:25Z

This adds no functionality directly, but is a useful starting point for adding new repair functionality. Signed-off-by: Daniel Kahn Gillmor

lib: run uncrustify

2019-06-14T10:41:27Z

This is the result of running $ uncrustify --replace --config ../devel/uncrustify.cfg *.c *.h *.cc in the lib directory

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/database: index user headers.

2019-05-25T10:21:13Z

This essentially involves calling _notmuch_message_gen_terms once for each user defined header.

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.

lib: cache user prefixes in database object

2019-05-25T10:08:20Z

This will be used to avoid needing a database access to resolve a db prefix from the corresponding UI prefix (e.g. when indexing). Arguably the setup of the separate header map does not belong here, since it is about indexing rather than querying, but we currently don't have any other indexing setup to do.

lib: setup user headers in query parser

2019-05-25T09:56:16Z

These tests will need to be updated if the Xapian query print/debug format changes.

lib: add _notmuch_message_id_parse_strict

2018-09-06T11:07:13Z

The idea is that if a message-id parses with this function, the MUA generating it was probably sane, and in particular it's probably safe to use the result as a parent from In-Reply-to.