Mercurial > emacs
comparison man/mini.texi @ 67395:9768435a278a
(Completion Commands, Completion):
In file name input, SPC does not do completion.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Thu, 08 Dec 2005 17:58:35 +0000 |
parents | 83e12e37521d |
children | eab2da67a471 7beb78bc1f8e |
comparison
equal
deleted
inserted
replaced
67394:f18c2431b06b | 67395:9768435a278a |
---|---|
196 into a longer string that it stands for, by matching it against a set of | 196 into a longer string that it stands for, by matching it against a set of |
197 @dfn{completion alternatives} provided by the command reading the | 197 @dfn{completion alternatives} provided by the command reading the |
198 argument. @kbd{?} is defined to display a list of possible completions | 198 argument. @kbd{?} is defined to display a list of possible completions |
199 of what you have inserted. | 199 of what you have inserted. |
200 | 200 |
201 For example, when @kbd{M-x} uses the minibuffer to read the name of a | 201 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 | 202 a command, it provides a list of all available Emacs command names to |
203 complete against. The completion keys match the minibuffer text | 203 complete against. The completion keys match the minibuffer text |
204 against all the command names, find any additional name characters | 204 against all the command names, find any additional name characters |
205 implied by the ones already present in the minibuffer, and add those | 205 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 | 206 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 | 207 to type @kbd{M-x ins @key{SPC} b @key{RET}} instead of @kbd{M-x |
208 insert-buffer @key{RET}} (for example). | 208 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.) | |
209 | 211 |
210 Case is normally significant in completion, because it is significant | 212 Case is normally significant in completion, because it is significant |
211 in most of the names that you can complete (buffer names, file names and | 213 in most of the names that you can complete (buffer names, file names and |
212 command names). Thus, @samp{fo} does not complete to @samp{Foo}. | 214 command names). Thus, @samp{fo} does not complete to @samp{Foo}. |
213 Completion does ignore case distinctions for certain arguments in which | 215 Completion does ignore case distinctions for certain arguments in which |
258 @table @kbd | 260 @table @kbd |
259 @item @key{TAB} | 261 @item @key{TAB} |
260 Complete the text before point in the minibuffer as much as possible | 262 Complete the text before point in the minibuffer as much as possible |
261 (@code{minibuffer-complete}). | 263 (@code{minibuffer-complete}). |
262 @item @key{SPC} | 264 @item @key{SPC} |
263 Complete the minibuffer text before point, but don't go beyond one word | 265 Complete the minibuffer text before point, but don't go beyond one |
264 (@code{minibuffer-complete-word}). | 266 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. | |
265 @item @key{RET} | 269 @item @key{RET} |
266 Submit the text in the minibuffer as the argument, possibly completing | 270 Submit the text in the minibuffer as the argument, possibly completing |
267 first as described | 271 first as described |
268 @iftex | 272 @iftex |
269 in the next subsection (@code{minibuffer-complete-and-exit}). | 273 in the next subsection (@code{minibuffer-complete-and-exit}). |