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.
---
Please CC me in replies; I am not subscribed to the list.
 lib/notmuch.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/lib/notmuch.h b/lib/notmuch.h
index 95918fc2..080795ff 100644
--- a/lib/notmuch.h
+++ b/lib/notmuch.h
@@ -807,6 +807,12 @@ notmuch_database_get_directory (notmuch_database_t 
*database,
  * notmuch_message_destroy when done with the message. On any failure
  * '*message' will be set to NULL.
  *
+ * Note that this does not synchronised Maildir flags to notmuch flags,
+ * regardless of the value of maildir.synchronize_flags. Future calls to
+ * notmuch-new(1) will also not synchronise flags, since the file's current
+ * mtime shall be recorded as indexed. If flags ought to be synchronised,
+ * explicitly call notmuch_message_maildir_flags_to_tags.
+ *
  * Return value:
  *
  * NOTMUCH_STATUS_SUCCESS: Message successfully added to database.
-- 
2.52.0


_______________________________________________
notmuch mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to