From 17ae356e35406128ab6eeb77496bca01fded4f6c Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Thu, 12 Aug 2021 20:34:26 +0300 Subject: [PATCH] mu4e: Fix up documentation And remove some unncessary message --- mu4e/mu4e-utils.el | 10 +++------- mu4e/mu4e-vars.el | 14 +++----------- 2 files changed, 6 insertions(+), 18 deletions(-) diff --git a/mu4e/mu4e-utils.el b/mu4e/mu4e-utils.el index 8c143314..60c3eae9 100644 --- a/mu4e/mu4e-utils.el +++ b/mu4e/mu4e-utils.el @@ -644,13 +644,9 @@ process." "Indexing... processed %d, updated %d" processed updated) (progn (mu4e-index-message - "%s completed; processed %d, updated %d, cleaned-up %d%s" + "%s completed; processed %d, updated %d, cleaned-up %d" (if mu4e-index-lazy-check "Lazy indexing" "Indexing") - processed updated cleaned-up - (if (and mu4e-index-lazy-check - (not (eq mu4e-index-lazy-check 'lazy)) - (= 0 updated)) - " (consider M-x mu4e-update-nonlazy)" "")) + processed updated cleaned-up) ;; call the updated hook if anything changed. (unless (zerop (+ updated cleaned-up)) (run-hooks 'mu4e-index-updated-hook)) @@ -957,7 +953,7 @@ Also scrolls to the final line, and update the progress throbber." This is just a convenience wrapper for indexing the non-lazy way if you otherwise want to use `mu4e-index-lazy-check'." (interactive) - (let ((mu4e-index-cleanup nil) (mu4e-index-lazy-check nil)) + (let ((mu4e-index-cleanup t) (mu4e-index-lazy-check nil)) (mu4e-update-index))) diff --git a/mu4e/mu4e-vars.el b/mu4e/mu4e-vars.el index bf1d5e6e..db3a60a7 100644 --- a/mu4e/mu4e-vars.el +++ b/mu4e/mu4e-vars.el @@ -133,17 +133,9 @@ needs (re)indexing or not. When this is set to non-nil, mu only uses the directory timestamps to decide whether it needs to check the messages -beneath it. This makes indexing much faster, but has some -limitations: since directory timestamp changes do not traverse -upwards and therefore this does not see changes in -sub-directories: a change in 'bar' in 'Maildir/foo/bar/...' is -not detected, only a change in 'foo'. In that case, this option -should not be set. - -Note: if no updated/new message were found during the lazy check, -mu4e will suggest using `mu4e-update-index-nonlazy'; if you do -not wish to see that suggestion, set `mu4e-index-lazy-check' to the -symbol `lazy'." +beneath it. This makes indexing much faster, but might miss some +changes. For this, you might want to occasionally call +`mu4e-update-index-nonlazy'." :type 'boolean :group 'mu4e :safe 'booleanp)