alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

New flexible method of customising completing-read

Browse Source 
Added the customisation option 'mu4e-completing-read-function' which can
be used to choose which method of input-with-completion will be used by
mu4e. This variable is set to the function which mu4e will use.

By default, mu4e will use ido (via 'ido-completing-read'), but any
compatible completing-read function can be used instead. Interesting
choices would include 'helm-comp-read' for Helm-based completion, and
'completing-read' for the built-in basic completion system.
This commit is contained in:
Stuart Hickinbottom
2013-09-12 22:42:45 +01:00
parent 97e821bcd6
commit 6e8e9ec44a
2 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
mu4e/mu4e-vars.el
View File

@ -176,6 +176,19 @@ view buffer."
:type 'boolean
:group 'mu4e)
(defcustom mu4e-completing-read-function 'ido-completing-read
"Function to be used to receive input from the user with
completion. This is used to receive the name of the maildir
to switch to via `mu4e~headers-jump-to-maildir'.
Suggested possible values are:
* `completing-read': built-in completion method
* `ido-completing-read': dynamic completion within the minibuffer
* `helm-comp-read': dynamic completion within popup window"
:type 'function
:options '(completing-read ido-completing-read helm-comp-read)
:group 'mu4e)
;; crypto
(defgroup mu4e-crypto nil
"Crypto-related settings."