- add mu4e-toggle-logging to enable/disable logging
- add mu4e-show-log to view the log buffer, and bind it to '$' in the
main/header/view buffers
- add a note about it to the doc (mu4e.texi)
- make mu4e-log the the new logging function, use colors to distinguish
incoming/outgoing data
- only keep last 1200 lines of log in the log buffer
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