- The queue-related actions of `mu4e~main-view-real` have been extracted
to their own `mu4e~main-view-queue` method.
- The queue toggling action now has the word "currently" to easily.
distinguish between the current state and the toggle (e.g., "currently
queued" instead of just "queued").
- The "[f]lush queued emails" is only visible if there is at least 1
email in the queue.
- The number of emails in the queue is visible in the flushing
action (e.g., "[f]lush 10 queued emails").
mu:run-stats expects the passed-in function to take 3 arguments. The
third argument applies to gnuplot only, which is not applicable to the
count function in msgs-count.scm.
This example shows how to archive and mark a message as read which emphasizes
the importance of order in tagging a message before anything else due to the
implementation of tagging (since it currently uses 'sed').
Previously, the behavior of mu4e-view-headers-next-unread was that the cursor moved in the headers view but did not change the highlight nor the message in the view buffer. This patch updates the function to also select the message in the view buffer which appears to also highlight the message correctly in the header view.
This allows to re-tag a message in a mark action.
Two examples of what one can do with this stuff:
1. G-mail archiving:
(archive
:char "a"
:prompt "archive"
:show-target (lambda (target) "archive")
:action (lambda (docid msg target)
(mu4e~proc-move docid nil "-N")
(mu4e-action-retag-message msg "-\\Inbox")))
2. Tagging:
(tag
:char "g"
:prompt "gtag"
:ask-target (lambda () (read-string "What tag do you want to add?"))
:show-target (lambda (target) target)
:action (lambda (docid msg target)
(mu4e~proc-move docid nil "-N")
(mu4e-action-retag-message msg (concat "+" target))))
Add two new customization variables:
mu4e-index-update-error-continue
mu4e-index-update-error-warning
With these, we can configure what happens when the mail-retrieval
program finishes with a non-zero exit code.
Make the default to warn but continue; it seems quite some users got
bitten by the old behavior of not updating after an error (which may
only be a pseudo-error). offlineimap/mbsync do not document their exit
codes very well, unlike fetchmail.
Also update manual for this.