184 |
can be determined from the part you have typed. |
can be determined from the part you have typed. |
185 |
|
|
186 |
When completion is available, certain keys---@key{TAB}, @key{RET}, and |
When completion is available, certain keys---@key{TAB}, @key{RET}, and |
187 |
@key{SPC}---are rebound to complete the text present in the minibuffer |
@key{SPC}---are rebound to complete the text in the minibuffer before point |
188 |
into a longer string that it stands for, by matching it against a set of |
into a longer string that it stands for, by matching it against a set of |
189 |
@dfn{completion alternatives} provided by the command reading the |
@dfn{completion alternatives} provided by the command reading the |
190 |
argument. @kbd{?} is defined to display a list of possible completions |
argument. @kbd{?} is defined to display a list of possible completions |
192 |
|
|
193 |
For example, when @kbd{M-x} uses the minibuffer to read the name of a |
For example, when @kbd{M-x} uses the minibuffer to read the name of a |
194 |
command, it provides a list of all available Emacs command names to |
command, it provides a list of all available Emacs command names to |
195 |
complete against. The completion keys match the text in the minibuffer |
complete against. The completion keys match the minibuffer text |
196 |
against all the command names, find any additional name characters |
against all the command names, find any additional name characters |
197 |
implied by the ones already present in the minibuffer, and add those |
implied by the ones already present in the minibuffer, and add those |
198 |
characters to the ones you have given. This is what makes it possible |
characters to the ones you have given. This is what makes it possible |
245 |
|
|
246 |
@table @kbd |
@table @kbd |
247 |
@item @key{TAB} |
@item @key{TAB} |
248 |
Complete the text in the minibuffer as much as possible |
Complete the text before point in the minibuffer as much as possible |
249 |
(@code{minibuffer-complete}). |
(@code{minibuffer-complete}). |
250 |
@item @key{SPC} |
@item @key{SPC} |
251 |
Complete the minibuffer text, but don't go beyond one word |
Complete the minibuffer text before point, but don't go beyond one word |
252 |
(@code{minibuffer-complete-word}). |
(@code{minibuffer-complete-word}). |
253 |
@item @key{RET} |
@item @key{RET} |
254 |
Submit the text in the minibuffer as the argument, possibly completing |
Submit the text in the minibuffer as the argument, possibly completing |
558 |
you can edit its expression as usual and then resubmit it by typing |
you can edit its expression as usual and then resubmit it by typing |
559 |
@key{RET} as usual. |
@key{RET} as usual. |
560 |
|
|
561 |
|
@vindex isearch-resume-enabled |
562 |
|
Incremental search does not, strictly speaking, use the minibuffer, |
563 |
|
but it does something similar, so normally it is treated as a complex |
564 |
|
command 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 |
|
|
568 |
@vindex command-history |
@vindex command-history |
569 |
The list of previous minibuffer-using commands is stored as a Lisp |
The list of previous minibuffer-using commands is stored as a Lisp |
570 |
list in the variable @code{command-history}. Each element is a Lisp |
list in the variable @code{command-history}. Each element is a Lisp |