alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mu4e: mention database-caching in FAQ

Browse Source 
As a reason for discrepancies between mu and mu4e results; as per #2741.
This commit is contained in:
Dirk-Jan C. Binnema
2024-08-16 20:28:29 +02:00
parent 52e388923f
commit e04d1cf42c
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
mu4e/mu4e.texi
View File

@ -4070,6 +4070,11 @@ answers.
and @t{mu4e} should yield the same results. If they differ, this is and @t{mu4e} should yield the same results. If they differ, this is
usually because one of the following reasons: usually because one of the following reasons:
@itemize @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: @item different options:
@t{mu4e} defaults to having @t{mu4e-headers-include-related}, and @t{mu4e} defaults to having @t{mu4e-headers-include-related}, and
@t{mu4e-headers-results-limit} set to 500. However, the command-line @t{mu4e-headers-results-limit} set to 500. However, the command-line