featurep! will be renamed modulep! in the future, so it's been
deprecated. They have identical interfaces, and can be replaced without
issue.
featurep! was never quite the right name for this macro. It implied that
it had some connection to featurep, which it doesn't (only that it was
similar in purpose; still, Doom modules are not features). To undo such
implications and be consistent with its namespace (and since we're
heading into a storm of breaking changes with the v3 release anyway),
now was the best opportunity to begin the transition.
Thanks to some combination of ignorance and obstinance, mu4e has thrown
compatibility to the wind and completely ignored the exitance of
define-obsolete-function-alias. Coupled with the inconsistent/partial
function renaming, this has made the mu4e 1.6⟶1.8 change particularly
annoying to deal with.
By suffering the pain of doing the mu4e author's work for them, we can
use defalias to give backwards compatibility a good shot for about 60
functions. Some mu4e~x functions are now mu4e--x, others are unchanged,
and then you've got a few odd changes like mu4e~proc -> mu4e--server and
mu4e-search-rerun. The form of message :from entries has also changed,
and a new (mu4e) entrypoint added supplanting mu4e~start.
Fix: #6511Close: #6549
Co-authored-by: Rahguzar <aikrahguzar@gmail.com>
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.
The user can configure a list of addresses that are associated with a
context by passing a list to set-email-account!, e.g.
(set-email-account! "foo"
...
(+mu4e-personal-addresses ("foo@bar.org" "bar@baz.org")))
This list, if it exists, is used to prompt the user for the "from"
address after trying to set the "from" address automatically.
- stylistic tweaks
- make accent colour easily user-settable
- scale LaTeX fragments appropriately
- make it easy to toggle org-msg-mode for one-off messages
mu4e 1.4 brings quite a few changes, including the deprecation of
previously used variables. These are now guarded by a version
comparison. org-mu4e is not needed for linking anymore,
org-mu4e-link-query-in-headers-mode was renamed. It's new version
defaults to nil and is therefore not set anymore -- I am not sure if the
default was changed or setting it was not strictly needed previously.
