emacs
/
mu
mirror of https://github.com/djcb/mu.git
1
0
Fork 0
Code Issues Releases Wiki Activity

mu4e: Fix up documentation 

And remove some unncessary message
This commit is contained in:
Dirk-Jan C. Binnema 2021-08-12 20:34:26 +03:00
parent b465c1f779
commit 17ae356e35
2 changed files with 6 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
mu4e/mu4e-utils.el
View File

@ -644,13 +644,9 @@ process."
"Indexing... processed %d, updated %d" processed updated) "Indexing... processed %d, updated %d" processed updated)
(progn (progn
(mu4e-index-message (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") (if mu4e-index-lazy-check "Lazy indexing" "Indexing")
processed updated cleaned-up 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)" ""))
;; call the updated hook if anything changed. ;; call the updated hook if anything changed.
(unless (zerop (+ updated cleaned-up)) (unless (zerop (+ updated cleaned-up))
(run-hooks 'mu4e-index-updated-hook)) (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 This is just a convenience wrapper for indexing the non-lazy way
if you otherwise want to use `mu4e-index-lazy-check'." if you otherwise want to use `mu4e-index-lazy-check'."
(interactive) (interactive)
(let ((mu4e-index-cleanup nil) (mu4e-index-lazy-check nil)) (let ((mu4e-index-cleanup t) (mu4e-index-lazy-check nil))
(mu4e-update-index))) (mu4e-update-index)))

14
mu4e/mu4e-vars.el
View File

@ -133,17 +133,9 @@ needs (re)indexing or not.
When this is set to non-nil, mu only uses the directory When this is set to non-nil, mu only uses the directory
timestamps to decide whether it needs to check the messages timestamps to decide whether it needs to check the messages
beneath it. This makes indexing much faster, but has some beneath it. This makes indexing much faster, but might miss some
limitations: since directory timestamp changes do not traverse changes. For this, you might want to occasionally call
upwards and therefore this does not see changes in `mu4e-update-index-nonlazy'."
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'."
:type 'boolean :type 'boolean
:group 'mu4e :group 'mu4e
:safe 'booleanp) :safe 'booleanp)