On mac process args aren't defined, but comm is. Since comm also works
on Linux, we now check for that instead, accounting for a potential
capitalisation difference.
Mu4e 1.6 changes the signature of `mu4e-draft-open'. Since we don't care
about the args replace funcall with apply to make sure it's happy no
matter how many args it expected.
Modify +mu4e-set-from-address-h to account for messages with multiple
to/from headers by finding the intersection between the headers and
registered accounts.
While I'm at it, there was a rather silly typo in the when-let line
that's been corrected.
This hook should only be used when users define email aliases, or no
contexts are defined (in which case the list of personal addresses
should be used). Otherwise, the `:match-func` contexts feature is
sufficient.
This allows users to have different casing in their mu4e context names
and the corresponding directories. Since mu4e's context switching
automatically selects the letter from the context name, this allows
users to set two contexts starting with the same letter to uppercase and
lowercase variants, while leaving the directories lowercase.
The default-p argument to `set-email-account!` now works as intended.
mu4e checks the first context on startup to determine the default and
uses functions for that, so we can't really get around it by setting
the bare mu4e~context-current variable.
Recently org-msg gained the capability to change which exports/mime
types are sent based on the email, and a new utf-8 type. We will make
use of both of these additions.
On some OS implementations (e.g. BSD uses kqueue),
`file-notify-add-watch' might not create the file if it doesn't exist.
This patch fixes that error. Arguably, emacs lisp should ensure the same
behaviour exists across each implementation.
Emails sent to an @gmail.com account may have been forwarded to a non-gmail mailbox.
Thus the current approach is over-eager.
Only checking @gmail on send, and then matching a user's maildir (not email) with
received messages is a more robust approach.
To accommodate this we switch `+mu4e-gmail-addresses' out for `+mu4e-gmail-accounts'.
Along the way `mu4e-index-cleanup' and `mu4e-index-lazy-check' customisations were
moved into the readme as a recommendation for Gmail-only users, to avoid causing
adverse effects for users who have non-gmail accounts too.
