mu
and mu4e
differ - why?mu4e
as the default e-mail client in Emacs?mu4e
use some fancy Unicode instead of these boring plain-ASCII ones?mu4e
in the background?mu4e
support searching for CJK (Chinese-Japanese-Korean) characters?mu
and mu4e
differ - why? ¶In general, the same queries for mu
and mu4e
should yield the same results. If they differ, this is
usually because one of the following reasons:
mu4e
defaults to having mu4e-headers-include-related
, and
mu4e-headers-results-limit
set to 500. However, the command-line
mu find
’s corresponding --include-related
is false, and
there’s no limit (--maxnum
).
mu4e
and mu find
do
not both sort their results in the same direction.
*
) may be expanded by the shell before mu
ever
sees them, and the query may not be what you think it is. Quoting is
necessary.
For speed reasons, the counts do not exclude messages that no longer exist in the file-system, nor does it exclude duplicate messages; See mu-mu4e-differ.
You can select (’mark’ in Emacs-speak) messages, just like you would select text
in a buffer; the actions you then take (e.g., DEL for delete, m for
move and t for trash) apply to all selected messages. You can also use
functions like mu4e-headers-mark-thread
(T),
mu4e-headers-mark-subthread
(t) to mark whole threads at the same
time, and mu4e-headers-mark-pattern
(%) to mark all messages
matching a certain regular expression.
Yes you can — see the documentation for the variable
mu4e-headers-leave-behavior
.
mu4e
as the default e-mail client in Emacs? ¶See Default email client.
mu4e
use some fancy Unicode instead of these boring plain-ASCII ones? ¶Glad you asked! Yes, if you set mu4e-use-fancy-chars
to t
, mu4e
uses such fancy characters in a number of places. Since not all fonts include
all characters, you may want to install the unifont
and/or symbola
fonts
on your system.
mu4e
in the background? ¶Yes — if you provide a prefix-argument (C-u), mu4e
starts, but does
not show the main-window.
mu4e
support searching for CJK (Chinese-Japanese-Korean) characters? ¶Only partially. If you have Xapian
1.2.8 or newer, and set the environment
variable XAPIAN_CJK_NGRAM
to non-empty before indexing, both when using
mu
from the command-line and from mu4e
.
The mu4e-completing-read-function
variable can be customized to select a
folder in any way. The variable can be set to a function that receives five
arguments, following completing-read
. The default value is
ido-completing-read
; to use emacs’s default behavior, set the variable to
completing-read
. Helm users can use the same value, and by enabling
helm-mode
use helm-style completion.
Set mu4e-cache-maildir-list
to t
(make sure to read its
docstring).
See the variables mu4e-headers-hide-predicate
and
mu4e-headers-hide-enabled
. The latter can be toggled through
mu4e-headers-toggle-property
.
For example, to filter out GMail’s spam folder, set it to:
(setq mu4e-headers-hide-predicate (lambda (msg) (string-suffix-p "Spam" (mu4e-message-field msg :maildir))))
The error occurs because mu4e
is binding more variables than
emacs
allows for, by default. You can avoid this by setting a
higher value, e.g. by adding the following to your configuration:
(setq max-specpdl-size 5000)
Note that Emacs 29 obsoletes this variable.