198 |
argument. @kbd{?} is defined to display a list of possible completions |
argument. @kbd{?} is defined to display a list of possible completions |
199 |
of what you have inserted. |
of what you have inserted. |
200 |
|
|
201 |
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 |
202 |
command, it provides a list of all available Emacs command names to |
a command, it provides a list of all available Emacs command names to |
203 |
complete against. The completion keys match the minibuffer text |
complete against. The completion keys match the minibuffer text |
204 |
against all the command names, find any additional name characters |
against all the command names, find any additional name characters |
205 |
implied by the ones already present in the minibuffer, and add those |
implied by the ones already present in the minibuffer, and add those |
206 |
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 |
207 |
to type @kbd{M-x ins @key{SPC} b @key{RET}} instead of @kbd{M-x |
to type @kbd{M-x ins @key{SPC} b @key{RET}} instead of @kbd{M-x |
208 |
insert-buffer @key{RET}} (for example). |
insert-buffer @key{RET}} (for example). (@key{SPC} does not do |
209 |
|
completion in reading file names, because it is common to use spaces |
210 |
|
in file names on some systems.) |
211 |
|
|
212 |
Case is normally significant in completion, because it is significant |
Case is normally significant in completion, because it is significant |
213 |
in most of the names that you can complete (buffer names, file names and |
in most of the names that you can complete (buffer names, file names and |
262 |
Complete the text before point in the minibuffer as much as possible |
Complete the text before point in the minibuffer as much as possible |
263 |
(@code{minibuffer-complete}). |
(@code{minibuffer-complete}). |
264 |
@item @key{SPC} |
@item @key{SPC} |
265 |
Complete the minibuffer text before point, but don't go beyond one word |
Complete the minibuffer text before point, but don't go beyond one |
266 |
(@code{minibuffer-complete-word}). |
word (@code{minibuffer-complete-word}). @key{SPC} for completion is |
267 |
|
not available when entering a file name, since some users often put |
268 |
|
spaces in filenames. |
269 |
@item @key{RET} |
@item @key{RET} |
270 |
Submit the text in the minibuffer as the argument, possibly completing |
Submit the text in the minibuffer as the argument, possibly completing |
271 |
first as described |
first as described |