From e04d1cf42c0759caf6cf8f0ef25b53f875502fd3 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Fri, 16 Aug 2024 20:28:29 +0200 Subject: [PATCH] mu4e: mention database-caching in FAQ As a reason for discrepancies between mu and mu4e results; as per #2741. --- mu4e/mu4e.texi | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index d8e3166d..9b791e1d 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -4070,6 +4070,11 @@ answers. and @t{mu4e} should yield the same results. If they differ, this is usually because one of the following reasons: @itemize +@item Database caching: +changes in @t{mu4e} are not immediately visible in the command-line @t{mu}, +since it can take a while before changes are committed to disk (for performance +reasons). Note that quitting @t{mu4e} or invoking @t{mu4e-update-mail-and-index} +and @t{mu4e-update-index} trigger committing to disk as a side-effect. @item different options: @t{mu4e} defaults to having @t{mu4e-headers-include-related}, and @t{mu4e-headers-results-limit} set to 500. However, the command-line