| Age | Commit message (Collapse) | Author |
|
... in mu4e-compose-reply-include-mime-types, add text/x-diff as well.
|
|
mu4e-draft: add `{sign,encrypt}-signed-replies` to crypto options
|
|
Remember the exact frame we created, and only kill that one.
Ensure mu4e-compose-post-hook fires at most once.
|
|
After restoring the window configuration, we could end up pointing at
the wrong message.
Let's try harder to restore... issue #2902.
|
|
Another attempt at fixing the old #2722 decoding issue.
|
|
This should help when multiple compose windows are present, such as in
issue #2912.
|
|
This scratches an itch of mine: being able to sign messages when they're replies
to signed messages.
Signed-off-by: Sergio Durigan Junior <sergiodj@sergiodj.net>
|
|
When there are raw utf-8 headers.
Should help for #2722.
|
|
mu4e-compose-reply-include-mime-types specifies the mime-types for
message attachments that should be included in replies, with the default
set to "text/x-patch" -- i.e., patches are included in replies, so you
can comment on them.
As mentioned in #2896.
|
|
t by default (current behavior), but you can turn if off if your change (e.g.
compose-hook) wants to put the point in some different place.
|
|
Narrow to headers first, or we may remove e.g. Date: headers in
forwarded messages.
|
|
In non-parent messages, such as completely new message, ensure the
mu4e-compose-type is available during the initial composition, i.e.,
enlarge the let to cover the rest of `mu4e--prepare-draft'.
|
|
Ensure we can use both from headers view and message view.
This helps with "supersede".
|
|
Also a little refactoring.
This should hopefully help with diagnosing #2478.
|
|
Avoid the silly byte-compilation warning
|
|
This ensures fields (like Date:) are updated.
|
|
It seems the older (<= emacs 28 at least) message-hide-headers caused
trouble when editing drafts with mu4e in some cases.
So use the _newer_ version of this function, imported as
mu4e--message-hide-headers.
Fixes #2661.
|
|
This updates commit 411407f03e4bf55250d96015f427a86a373bfb12 and moves
the check to where we set the special headers.
|
|
* Set `message-newsreader' before calling `mu4e--prepare-draft-buffer' so that
`User-Agent' is properly set.
* Fixes #2750.
|
|
|
|
|
|
Ensure draft is removed also when there's no fcc-path. As suggested by
@malb in #2719.
|
|
Run the hook earlier, and ensure mu4e-compose-type &
mu4e-compose-parent-message are set.
As noted in #2715.
|
|
Set message-alternative-emails to the special
`mu4e-personal-or-alternative-address-p' such that it honors both
user-specified alternative address as well as the mu personal addresses.
Fixes #2708.
|
|
We should invoke it, as documented.
|
|
|
|
The variables mu4e-compose-parent-message & mu4e-compose-type are
buffer-local as well as permanent-local. That way, they'll survive the
mode change to mu4e-compose-mode and we can use them in the
corresponding mode-hook.
|
|
This seems necessary in some cases.
|
|
In mu4e-sent-messages-behavior.
Fixes #2701.
|
|
(again) avoid mixing up message-reply-headers.
|
|
A hook for when we're done with message composition.
We populate it with a function to kill created frames and one to attempt
to restore window configuration.
|
|
Reworked from the pull #2698 for the new branch.
|
|
Handle buffer display where all mu4e's buffer display is done: in mu4e-window.el.
Avoid overly long lines in mu4e-window.el.
|
|
Move draft-creation part of message-composition to a new file
mu4e-drafts
However, this is more than just some refactoring: rework the
message (draft) setup as such to ensure we always get a (non-active,
live) buffer back from the composition process.
This also fixes
(progn
(compose-mail "test@example.org" "Test")
(insert "TEST"))
as mentioned on the mailing list.
Fixes #2699
|
|
This is a new composer sub-system, which more closely follows
Gnus/message; in particular, we let gnus take care of creating draft
messages.
This reduces code size and allows us to re-use some of the more advanced
features.
There are a number of user-visible changes:
- `mu4e-compose-resend' directly uses `message-resend', so there is no
more editing phase (which used to be a bit broken with re-encoding
MIME messages.
|
|
|
|
Try to make useful descriptions and use conventional --- to separate filename
from description.
|
|
Fixes https://github.com/djcb/mu/issues/2535
|
|
|
|
- Bug fix.
- Reply-all consistency, related to #2524
|
|
* mu4e/mu4e-draft.el
(mu4e-compose-reply-recipients): (mu4e-compose-reply-to-address):
* mu4e/mu4e-thread.el (mu4e-thread-fold-single-children): Clarify
docstrings and fixed type definitions.
|
|
So that the type definitions reflects the docstrings more closely. In additon,
fixed warnings from flymake about docstring.
* mu4e/mu4e-draft.el
mu4e-compose-keep-self-cc: should be a comma
* mu4e/mu4e-folders.el
mu4e-maildir-shortcuts: recognize new (plist) format
* mu4e/mu4e-helpers.el
mu4e-debug: removed unnecessary double space in docstring
* mu4e/mu4e-query-items.el
mu4e-query-rewrite-function: prepend "\\=" before column 0 "(" in docstring
* mu4e/mu4e-search.el
mu4e-search-sort-field mu4e-search-sort-direction: used radio in types
* mu4e/mu4e-server.el
mu4e-mu-binary: "mu" executable must exist
* mu4e/mu4e-view.el
mu4e-view-fields: fixed type
mu4e-view-actions: for function refs, prefer "#'" rather than "'"
|
|
Escape correctly.
|
|
Fixes #2420
|
|
Simple patch to fix #2403
|
|
Move out of mu4e-headers; rename variables and callers.
|
|
|
|
|
|
|
|
|