| Age | Commit message (Collapse) | Author |
|---|
|
Of course, after merging some problems come up.
Let's fix those first.
This reverts commit f2f01595a51380ae38aafb4cd11a0d3c17a33a10.
|
|
As per #2711.
|
|
This implements some rework of the way mu writes to the database; the
update ensures that everything goes through the "store-worker" which
maintains a queue, and does all the writes in a single (worker) thread;
this attempt to fix come cases of database corruption we say; or at
least make those a lot less likely
|
|
Update doccount after indexing.
|
|
So we can update doccount in mu4e after indexing
|
|
To ensure all Xapian rw commands happen in the same thread.
|
|
Use the store worker (-thread) to do all database modification.
Currently, the "removed" field of Progress is always 0.
|
|
store-worker is a thread + async queue to throttle requests to a single thread.
|
|
Simplify xapian-db: locks should go elsewhere; transaction level add
too much complication.
|
|
For development / testing.
|
|
|
|
Useful for stuffing messages in async-queues
|
|
Ensure we use the user-specified batch-size immediately after db creation.
|
|
mu4e-sent-func was used internally (triggered by mu-server), but is no
longer in use, so let's remove it and mark as obsolete.
Obsolete its callers as well.
|
|
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.
|
|
|
|
|
|
|
|
Convenience function for saving the message-at-point.
|
|
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
|
|
|
|
scanner: don't skip directory entries with type `DT_UNKNOWN`
|
|
mu4e-compose-reply with a prefix argument replies to ALL
|
|
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.
|
|
This seems necessary in some cases.
|
|
In mu4e-sent-messages-behavior.
Fixes #2701.
|
|
|
|
(again) avoid mixing up message-reply-headers.
|
|
It's opportunistic: messages referred to be msgid may not exist, and
that's okay.
|
|
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.
|
|
So we use context and display settings.
|
|
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
|
|
temporarily remove the mu4e-sent-messages-behavior change, it comes
back in a slightly different way in the next commits.
|
|
Fix: Put sent mail in correct location when `mu4e-sent-messages-behavior` is a function
|
|
|
|
This commits fixes a regression introduced in
85bfe763362b95935a3967f6585e14b3f9890a70 , 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.
|
|
netbsd needs this explicitly, other systems let us get away without it.
|
