when another window is selected, such as in the case when using the
speedbar).
Also, some cleanup in message composition (that would deserve a separate
commit, but it's too late now...)
header buffer
When we're doing a search while the results of a previous search are still
coming in from the backend, this way we can tell the frontend that this is
the right time to clear the buffer (previously, sometimes the results would
be mixed).
By default, @t{mu4e} puts a copy of any messages you sent in the folder you
set for @code{mu4e-sent-folder}. In some case, this may not be what you want -
for example, when using GMail+@abbr{IMAP} (but @emph{not} with
GMail+@abbr{POP3}), this interferes with GMail's handling of the sent messages
folder, and you may end up with duplicate messages. For this, since @t{mu4e}
0.9.8.3, there is the variable @code{mu4e-sent-messages-behavior}, which takes
a symbol. The default is @code{'sent} which, as stated causes the message to
be copied to your sent-messages folder. Other possible values are
@code{'trash} (so the sent message is copied to the trash-folder
(@code{mu4e-trash-folder}), and @code{'delete} to simply discard the message
altogether.
- mu4e-main.el: mu4e-update-mail-show-window retrieves mail / updates
database, show output in split window (actual work is done by...:)
- mu4e.el: mu4e-update-mail retrieves mail, updates database,
asynchronously. Optionally, show output in a buffer
when `mu4e-update-interval' is non-nil and some integer, it calls
mu4e-update-mail every so many seconds.
- mu4e.texi: document this
- TODO: updated
etc. a buffer. From the docstring:
"What do to when user leaves the headers view (e.g. quit or doing
a new search). Value is one of the following symbols:
- ask (ask the user whether to ignore the marks)
- apply (automatically apply the marks before doing anything else)
- ignore (automatically ignore the marks without asking)."
the new mu4e-handle-marks uses this.
