mu4e-index-updated-hook, which gets triggered when the indexing process triggered sees an update (not just new mail though). To use this hook, put something like the following in your setup (assuming you have aplay and some soundfile, change as needed):
(add-hook 'mu4e-index-updated-hook (defun new-mail-sound () (shell-command "aplay ~/Sounds/boing.wav&")))
mu4e-get-mail-command? Use the literal string "true" (or don’t do anything, it’s the default) which then uses /bin/true (a command that does nothing and always succeeds). This makes getting mail a no-op, but the messages are still re-indexed.
mu: mu_store_new_writable: xapian error 'Unable to get write lock on ~/.mu/xapian: already locked
What to do about this? You get this error because the underlying Xapian database
is locked by some other process; it can be opened only once in read-write mode. There is not
much mu4e can do about this, but if is another
mu instance that is
holding the lock, you can ask it to (gracefully) terminate:
pkill -2 -u $UID mu # send SIGINT sleep 1 mu index
mu4e automatically restarts mu when it needs it. In practice, this seems to work quite well.
offlineimapuses IMAP’s UTF-7 for encoding non-ascii folder names, while mu expects UTF-8 (so, e.g. /まりも えお43 becomes /&MH4wijCCMEgwSg-). How can I make mu4e display such folders correctly? This is best solved by telling
offlineimapto use UTF-8 instead – see https://github.com/djcb/mu/issues/68#issuecomment-8598652.
some Japanese characters