Introduce a new variable, mu4e-compose-reply-ignore-address, which matches
addresses to be skipped when doing wide replies.
This is identical in behavior to messages-dont-reply-to-names from message.el
(which we default on).
This commit adds a global variable
mu4e-compose-forward-as-attachment. To enable choosing forwarding
method on a per-message basis would probably require either:
• changing the mu server backend so that it distinguishes between
inline forwarding and forwarding as attachment;
• changing the mu server backend so that it doesn’t return attachments
at all and making both inline and as attachment forwarding via
MIME (and also making mu4e actually display MIME-enclosed inline
emails).
mu4e was making a vain attempt to fontify the compose buffer; this
doesn't work because message (from which mu4e-compose-mode derives) uses
font-locking for that.
So, instead, remap the message-mode faces to the ones used for mu4e.
As discussed in issue #751, mu4e should tried to accommodate some
different ways of choosing the context.
We add a new policy `ask-if-none', that will only query the user if
there is no context yet; this is the new default for
mu4e-context-policy, i.e. what happens when entering the main view.
The default policy for mu4e-compose-context-policy is now `ask',
i.e. ask if none of the contexts match.
The idea is for the defaults to ask when we don't know a context, and we
can't determine one using the match functions; this is probably the
least confusing. When user gets annoyed by too many question, they can
tweak the behavior to their liking. I.e. 'ask questions first, shoot
later'
Document all of this.
It seems some tools try to interpret the filename of message files,
even though they shouldn't:
"Do not try to extract information from unique names."
In particular, they seem to interpret the first part of the name (before
the first dot) as the # of seconds since the Unix epoch (ie.,
time(NULL)). That's not what mu/mu4e put there.
So, let's conform a bit more to the expected filename (as per the
maildir spec), so we're not confusing those tools.
So that one can see when a draft was composed when browsing the
draft maildir (instead of getting "None" in the Date column). Then one
can sort the drafts by date.
What was going wrong?
Using the function `mu4e-view-message-text',
mu4e~draft-cite-original created a temporary buffer. Based on this
buffer the function message-cite-original-without-signature,
borrowed from Gnus, had to extract the date for the citation
line. The problem was, that this function depends on a standardized
date in ISO format whilst mu4e-view-message-text formatted the date
according to the setting of mu4e-view-date-format.
This patch hopefully solves this problem by setting
mu4e-view-date-format in function mu4e~draft-cite-original.
