notmuch/lib, branch masterthread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=master2026-02-15T22:24:18Zlib/config: add config keys for git-remote-notmuch.2026-02-15T22:24:18ZDavid Bremnerdavid@tethera.net2026-01-24T22:56:34Zurn:sha1:b222d18634e95b54010cec02e994d3cc96755746
The precise function will be explained in a future update to
notmuch-config(1).
Document that indexing does not sync flags2026-02-15T22:20:22ZHugo Osvaldo Barrerahugo@whynothugo.nl2026-02-09T19:04:42Zurn:sha1:b8fa14f8a8f3e30c95f1dad54daa79a6a962fa73
This quirk is somewhat unexpected, since flags won't be updated as
expected, but subsequence calls to notmuch-new(1) won't update the
index, giving an impression of it being stale.
indexopts: avoid a memleak in the error path2026-02-08T00:19:36ZAnton Khirnovanton@khirnov.net2026-02-07T17:47:16Zurn:sha1:7557b6a1d47b5caa8dfced9d210d4d552b795c14lib: bump minor version2026-01-17T00:22:58ZDavid Bremnerdavid@tethera.net2026-01-17T00:14:30Zurn:sha1:fcf3b17d168840047ed0a4f095642a4eceb36ae3
This reflects the addition of a new API functions,
notmuch_{messages,threads}_status
lib: move call to _n_m_invalidate_metadata2026-01-14T22:18:24ZDavid Bremnerdavid@tethera.net2024-09-01T15:41:40Zurn:sha1:8f9e16f2b9a46bef2c7398a27ff29db7bb23ee8d
It is wrong most of the time in _notmuch_message_remove_terms, but
that function is too low level to know how to call
_n_m_invalidate_metadata with the right argument, at least not without
more extensive changes. This change merely makes the current behaviour
more obvious, since the other calls cannot have relied on metadata
being invalidated.
open: avoid leaking index_as_text regex objects2025-11-09T12:05:30ZAnton Khirnovanton@khirnov.net2025-10-17T07:51:50Zurn:sha1:5c921b6c0b2df460c7d50f6563edf700d0420732
Regexes compiled with regcomp() need to be freed with regfree(). Do that
in a talloc destructor attached to the compiled regex array.
Amended by db: Use C style comment. Add blank line per uncrustify.
lib: return NOTMUCH_STATUS_OPERATION_INVALIDATED where appropriate2025-08-09T10:12:23ZAnton Khirnovanton@khirnov.net2025-08-06T05:43:06Zurn:sha1:aa761727999b105711ba4ca789e0836a0a05cf9f
The overall goal is to allow clients to restart operations in
situations where that is the response recommended by the underlying
Xapian library.
Amended-by: db, added above explanation
lib/database-private: undef XAPIAN_DEPRECATED before redefining it2025-08-04T13:44:52ZAnton Khirnovanton@khirnov.net2025-07-27T14:11:47Zurn:sha1:bee7a53194606757997f069f0e95ac862fbba0e0
Silences compiler warnings about redefining a macro.
lib: add notmuch_threads_status()2025-08-04T13:43:35ZAnton Khirnovanton@khirnov.net2025-07-28T14:26:56Zurn:sha1:11d373b4fd05f5409bf5c49459fe141d2235f7f5
While a number of errors can happen when iterating over threads
(DatabaseModifiedError, memory allocation errors, etc.), the API
currently cannot signal them to the caller, and either triggers an
internal error (aborting the caller) or returns NULL from
notmuch_threads_get() with no information on what actually went wrong.
Add a new public function notmuch_threads_status() - similar to
previously added notmuch_messages_status() - that allows propagating
those errors to the caller.
Use this to remove the INTERNAL_ERROR() in _notmuch_thread_create()
(triggered by T642).
Fixes: https://github.com/pazz/alot/issues/1460
Amended-By: db. Resolved whitespace disagreement between emacs and
uncrustify in favour of uncrustify.
lib/config: simplify cleanup in notmuch_database_get_config_list()2025-08-04T13:15:38ZAnton Khirnovanton@khirnov.net2025-07-27T14:11:44Zurn:sha1:2e87a00f3909e7f5ddd3b51230d8b9483efbf380
The list destructor is always set when necessary (i.e. if the iterator
is successfully created), so there is never a need to invoke it
explicitly, even on failure.