Add store::consume_message, which is like add message but std::move from
the caller such that the messages longer has copies (with
Xapian::Document) on the caller side; this is to avoid threading issues.
Seems journal logging fails on NetBSD (no surprise), but has some
unwanted/not-fully-understood side-effects.
In any case, outside Linux there's no use in even trying to use
journald; so we don't do that anymore.
Add conditional support for syslog (requires glib 2.80).
New version 1.12.5
- Rework message composition; split off parts into mu4e-draft.el
This tries harder to maintain the current buffer as expected
- This fixes e.g. emacs-report-bug handling
- New hook mu4e-compose-post-hook for tweaking what mu4e does when
we're done with a message (after sending, cancelling, ...).
By default, it tries to close the frame if needed, and restore
the window configuration. See its docstring.
- Better handle forwarding of encoded messages
- Don't remove non-mu4e completion in composer
- Integrate iCalendar support with message-composition
- Handle mu4e-sent-messages-behavior correctly when it's a function
- Better support NetBSD
- Support some file systems that don't put the file type in d_type
- Improve documenation
According to the readdir(2) man-page, not all file-systems support returning the
entry's file-type in `d_type`. For example, the reprotest reproducibility tool,
uses the disorderfs FUSE file-system to shuffle the order in which directory
entries are returned, and this does not set `d_type`. Therefore, in addition to
entries with type `DT_DIR` and `DT_LNK`, also process entries with type
`DT_UNKNOWN`.
Signed-off-by: Jeremy Sowden <azazel@debian.org>
Seemingly, message-forwarded needs the raw message, not the decode one
for proper forwarding when the parent message is encoded in some way.
Add a little hack / workaround for that.
See #2662.
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.
Only include xapian.h in one place, so we can have consistent options.
With that in place, we can enable C++ move semantics.
We don't do anything with that yet, but we check in the meson.build file
to see if we have the required xapian version.
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.
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 commits fixes a regression introduced in
85bfe76336 , at which point sent mails ended up in
the "cur/" subdirectory of the root maildir when the mu4e-sent-messages-behavior
user option was set to a function.
When enabled, attempt mu4e's auto-completion the first in line (in
completion-at-point-functions); but don't remove any other completions
the user may have set up.
Fixes#2697.
- query when quitting emacs with unhandled marks in a headers buffer
- fix mime-handling
- update sent handling (simplifying it)
- some internal improvements
- number of small fixes / updates
- documentation updates
- re-enable a specific database lock; this makes indexing a bit slower,
but hopefully avoids some db corruption.
The function 'gnus-summary-bookmark-make-record' does not work properly with the
faux "appeasement" summary buffer, causing undesired changes in the window
configuration when the message rendering buffer's bookmark function is
called (which some packages, like Activities, Burly, and Dogears do routinely).
See <https://github.com/alphapapa/activities.el/issues/55>.
Reported-by: Daniel Goldin <https://github.com/danielgoldin>
