From 0087440a191a2609e5f2dc1fdfb81e4da0ca075d Mon Sep 17 00:00:00 2001 From: Maximilian Matthe Date: Thu, 28 Jan 2016 19:34:29 +0100 Subject: [PATCH] mu4e: fix mu4e-completing-read-function in doc Small doc fix. --- mu4e/mu4e.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 61e6c194..00a6d868 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -3627,7 +3627,7 @@ Yes, if you have @t{Xapian} 1.2.8 or newer, and set the environment variable @t{XAPIAN_CJK_NGRAM} to non-empty before indexing, both when using @t{mu} from the command-line and from @t{mu4e}. @item @emph{How can I customize the function to select a folder?} -The @t{mu4e-completing-read} variable can be customized to select a +The @t{mu4e-completing-read-function} variable can be customized to select a folder in any way. The variable can be set to a function that receives five arguments, following @t{completing-read}. The default value is @code{ido-completing-read}; to use emacs's default behaviour, set the