aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--man/mini.texi15
1 files changed, 11 insertions, 4 deletions
diff --git a/man/mini.texi b/man/mini.texi
index 86793e3ec38..88aac3bdc74 100644
--- a/man/mini.texi
+++ b/man/mini.texi
@@ -184,7 +184,7 @@ argument, then Emacs visibly fills in the rest, or as much as
184can be determined from the part you have typed. 184can be determined from the part you have typed.
185 185
186 When completion is available, certain keys---@key{TAB}, @key{RET}, and 186 When completion is available, certain keys---@key{TAB}, @key{RET}, and
187@key{SPC}---are rebound to complete the text present in the minibuffer 187@key{SPC}---are rebound to complete the text in the minibuffer before point
188into a longer string that it stands for, by matching it against a set of 188into a longer string that it stands for, by matching it against a set of
189@dfn{completion alternatives} provided by the command reading the 189@dfn{completion alternatives} provided by the command reading the
190argument. @kbd{?} is defined to display a list of possible completions 190argument. @kbd{?} is defined to display a list of possible completions
@@ -192,7 +192,7 @@ of what you have inserted.
192 192
193 For example, when @kbd{M-x} uses the minibuffer to read the name of a 193 For example, when @kbd{M-x} uses the minibuffer to read the name of a
194command, it provides a list of all available Emacs command names to 194command, it provides a list of all available Emacs command names to
195complete against. The completion keys match the text in the minibuffer 195complete against. The completion keys match the minibuffer text
196against all the command names, find any additional name characters 196against all the command names, find any additional name characters
197implied by the ones already present in the minibuffer, and add those 197implied by the ones already present in the minibuffer, and add those
198characters to the ones you have given. This is what makes it possible 198characters to the ones you have given. This is what makes it possible
@@ -245,10 +245,10 @@ when completion is available.
245 245
246@table @kbd 246@table @kbd
247@item @key{TAB} 247@item @key{TAB}
248Complete the text in the minibuffer as much as possible 248Complete the text before point in the minibuffer as much as possible
249(@code{minibuffer-complete}). 249(@code{minibuffer-complete}).
250@item @key{SPC} 250@item @key{SPC}
251Complete the minibuffer text, but don't go beyond one word 251Complete the minibuffer text before point, but don't go beyond one word
252(@code{minibuffer-complete-word}). 252(@code{minibuffer-complete-word}).
253@item @key{RET} 253@item @key{RET}
254Submit the text in the minibuffer as the argument, possibly completing 254Submit the text in the minibuffer as the argument, possibly completing
@@ -558,6 +558,13 @@ of saved entire commands. After finding the desired previous command,
558you can edit its expression as usual and then resubmit it by typing 558you can edit its expression as usual and then resubmit it by typing
559@key{RET} as usual. 559@key{RET} as usual.
560 560
561@vindex isearch-resume-enabled
562 Incremental search does not, strictly speaking, use the minibuffer,
563but it does something similar, so normally it is treated as a complex
564command and it appears in the history list for @kbd{C-x @key{ESC}
565@key{ESC}}. You can disable that by setting
566@code{isearch-resume-enabled} to @code{nil}.
567
561@vindex command-history 568@vindex command-history
562 The list of previous minibuffer-using commands is stored as a Lisp 569 The list of previous minibuffer-using commands is stored as a Lisp
563list in the variable @code{command-history}. Each element is a Lisp 570list in the variable @code{command-history}. Each element is a Lisp