From f460db362df4c519621494e950d47a5b76fa884d Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Fri, 12 Sep 2003 01:06:43 +0000 Subject: [PATCH] (Intro to Minibuffers): Explain that the minibuffer changes variables that record input events. (Minibuffer Misc): Add minibuffer-selected-window. --- lispref/minibuf.texi | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi index 44161c0178d..0e455a446e7 100644 --- a/lispref/minibuf.texi +++ b/lispref/minibuf.texi @@ -63,6 +63,11 @@ other window, when the minibuffer is not active. If the frame contains just a minibuffer, you can change the minibuffer's size by changing the frame's size. + Use of the minibuffer reads input events, and that alters the values +of variables such as @code{this-command} and @code{last-command} +(@pxref{Command Loop Info}). Your program should bind them around the +code that uses the minibuffer, if you do not want that to change them. + If a command uses a minibuffer while there is an active minibuffer, this is called a @dfn{recursive minibuffer}. The first minibuffer is named @w{@samp{ *Minibuf-0*}}. Recursive minibuffers are named by @@ -1660,6 +1665,12 @@ object. When the function @code{scroll-other-window} is called in the minibuffer, it scrolls this window. @end defvar +@defun minibuffer-selected-window +This function returns the window which was selected when the +minibuffer was entered. If selected window is not a minibuffer +window, it returns @code{nil}. +@end defun + Finally, some functions and variables deal with recursive minibuffers (@pxref{Recursive Editing}): -- 2.39.2