Commit 62812203 authored by Eli Zaretskii's avatar Eli Zaretskii
Browse files

Document the new feature of 'minibuffer-with-setup-hook'

* lisp/files.el (minibuffer-with-setup-hook): Clarify how FUN is
added to `minibuffer-setup-hook'.
parent 277d7efd
......@@ -647,8 +647,13 @@ respectively, `show-paren-when-point-inside-paren' or
These should be used in preference to `font-lock-fontify-buffer' when
called from Lisp.
** Macro `minibuffer-with-setup-hook' takes (:append FUN) to mean
appending FUN to `minibuffer-setup-hook'.
** Macro `minibuffer-with-setup-hook' can optionally append a function
to `minibuffer-setup-hook'.
If the first argument of the macro is of the form `(:append FUN)',
then FUN will be appended to `minibuffer-setup-hook', instead of
prepending it.
** cl-lib
*** New functions cl-fresh-line, cl-digit-char-p and cl-parse-integer.
......@@ -1431,8 +1431,10 @@ return value, which may be passed as the REQUIRE-MATCH arg to
(defmacro minibuffer-with-setup-hook (fun &rest body)
"Temporarily add FUN to `minibuffer-setup-hook' while executing BODY.
FUN can also be (:append FUN1), in which case FUN1 is appended to
By default, FUN is prepended to `minibuffer-setup-hook'. But if FUN is of
the form `(:append FUN1)', FUN1 will be appended to `minibuffer-setup-hook'
instead of prepending it.
BODY should use the minibuffer at most once.
Recursive uses of the minibuffer are unaffected (FUN is not
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment