Without creating some kind of a temporary name (which could then be
trivially renamed by the user as the current instructions say) a new
user trying to learn how to detach a view will run into this error when
switching to a new message after detaching:
[mu4e] Detached view buffer from *mu4e-headers*
funcall-interactively: No buffer named *mu4e-article*<2>
It seems like a good default and less friction to create a random name
automatically when detaching.
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 "'"
Fixed an issue where messages from mailing-list ("list" flag) were shown using
"s" in header view, which is also used for "signed" messages. Therefore changing
it to "L".
If the headers buffer isn't in a live window (e.g., mu4e-split-view
is 'single-window), get-buffer-window will return nil. In turn,
with-selected-window will die if fed a nil window, so default to using the
current window in this case.
This fixes a regression from c23dad7058 that
prevented using n/p from a view buffer.
Rebinding existing functions to different keys works fine, *but* it seems
some 3rd party code rebinds existing keys to different functions; that's
not really supported but use to half-work. Attempt to make it half-work
again, and document.
Instead of using mu4e's tradional completion UI, allow for delegating to
some implementation of completing-read.
Default
mu4e-read-option-use-builtin t
means that things work more-or-less as before.
Let the main-screen show a representation of the *actual* keybindings
rather than assuming the defaults.
For that to work, we need to invoke mu4e-main-mode earlier; add a new
hook mu4e-main-mode-rendered-hook which is invoked after rendering is
complete.
Add a few helpers for this to mu4e-helpers.
Dirk-Jan C. Binnema
Martin R. Albrecht
Nacho Barrientos
Sean Farley
ramon diaz-uriarte (at Phelsuma)
Ruijie Yu
Babak Farrokhi
Sean Allred
John Hamelink
Nicholas Vollmer
Anton Tetov
Al Haji-Ali
Leo Gaskin