Mercurial > emacs
comparison man/mini.texi @ 68458:eab2da67a471
Minor cleanups.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sun, 29 Jan 2006 16:59:14 +0000 |
parents | 9768435a278a |
children | dc2d5a6655a3 7432ca837c8d |
comparison
equal
deleted
inserted
replaced
68457:f54ada46e59e | 68458:eab2da67a471 |
---|---|
112 ignored in the example above, and you get the file | 112 ignored in the example above, and you get the file |
113 @file{/etc/termcap}. The ignored part of the file name is dimmed if | 113 @file{/etc/termcap}. The ignored part of the file name is dimmed if |
114 the terminal allows it; to disable this, turn off | 114 the terminal allows it; to disable this, turn off |
115 @code{file-name-shadow-mode} minor mode. | 115 @code{file-name-shadow-mode} minor mode. |
116 | 116 |
117 If you set @code{insert-default-directory} to @code{nil}, the default | 117 If you set @code{insert-default-directory} to @code{nil}, the |
118 directory is not inserted in the minibuffer. This way, the minibuffer | 118 default directory is never inserted in the minibuffer---so the |
119 starts out empty. But the name you type, if relative, is still | 119 minibuffer starts out empty. But the name you type, if relative, is |
120 interpreted with respect to the same default directory. | 120 still interpreted with respect to the same default directory. |
121 | 121 |
122 @node Minibuffer Edit | 122 @node Minibuffer Edit |
123 @section Editing in the Minibuffer | 123 @section Editing in the Minibuffer |
124 | 124 |
125 The minibuffer is an Emacs buffer (albeit a peculiar one), and the usual | 125 The minibuffer is an Emacs buffer (albeit a peculiar one), and the usual |
126 Emacs commands are available for editing the text of an argument you are | 126 Emacs commands are available for editing the text of an argument you are |
127 entering. | 127 entering. |
128 | 128 |
129 Since @key{RET} in the minibuffer is defined to exit the minibuffer, | 129 Since @key{RET} in the minibuffer is defined to exit the minibuffer, |
130 you can't use it to insert a newline in the minibuffer. To do that, | 130 you can't use it to insert a newline in the minibuffer. To do that, |
131 type @kbd{C-o} or @kbd{C-q C-j}. (On text terminals, newline is | 131 type @kbd{C-o} or @kbd{C-q C-j}. (The newline character is really the |
132 really the @acronym{ASCII} character control-J.) | 132 @acronym{ASCII} character control-J.) |
133 | 133 |
134 The minibuffer has its own window which always has space on the screen | 134 The minibuffer has its own window, which normally has space on the |
135 but acts as if it were not there when the minibuffer is not in use. When | 135 Emacs frame at all times, but it only acts like an Emacs window when |
136 the minibuffer is in use, its window is just like the others; you can | 136 the minibuffer is really in use. At those times, its window is much |
137 switch to another window with @kbd{C-x o}, edit text in other windows and | 137 like any other Emacs window; you can switch from the minibuffer window |
138 perhaps even visit more files, before returning to the minibuffer to submit | 138 to another window with @kbd{C-x o}, and edit text in other windows, |
139 the argument. You can kill text in another window, return to the | 139 before returning to the minibuffer to submit the argument. You can |
140 minibuffer window, and then yank the text to use it in the argument. | 140 kill text in another window, return to the minibuffer window, and then |
141 @xref{Windows}. | 141 yank the text to use it in the argument. @xref{Windows}. |
142 | 142 |
143 @cindex height of minibuffer | 143 @cindex height of minibuffer |
144 @cindex size of minibuffer | 144 @cindex size of minibuffer |
145 @cindex growing minibuffer | 145 @cindex growing minibuffer |
146 @cindex resizing minibuffer | 146 @cindex resizing minibuffer |
387 strings, then they are not ignored. Ignored extensions do not apply to | 387 strings, then they are not ignored. Ignored extensions do not apply to |
388 lists of completions---those always mention all possible completions. | 388 lists of completions---those always mention all possible completions. |
389 | 389 |
390 If an element of the list in @code{completion-ignored-extensions} ends | 390 If an element of the list in @code{completion-ignored-extensions} ends |
391 in a slash @file{/}, it indicates a subdirectory that should be ignored | 391 in a slash @file{/}, it indicates a subdirectory that should be ignored |
392 when completing file names. (Elements of | 392 when completing file names. Elements of |
393 @code{completion-ignored-extensions} which do not end in a slash are | 393 @code{completion-ignored-extensions} which do not end in a slash are |
394 never considered when a completion candidate is a directory; thus, | 394 never considered when a completion candidate is a directory; thus, |
395 completion returns directories whose names end in @file{.elc} even | 395 completion returns directories whose names end in @file{.elc} even |
396 though there's an element @code{".elc"} in the list.) | 396 though there's an element @code{".elc"} in the list. |
397 | 397 |
398 @vindex completion-auto-help | 398 @vindex completion-auto-help |
399 Normally, a completion command that cannot determine even one | 399 Normally, a completion command that cannot determine even one |
400 additional character automatically displays a list of all possible | 400 additional character automatically displays a list of all possible |
401 completions. If the variable @code{completion-auto-help} is set to | 401 completions. If the variable @code{completion-auto-help} is set to |
484 minibuffer as usual with @key{RET}. You can also edit the text before | 484 minibuffer as usual with @key{RET}. You can also edit the text before |
485 you reuse it; this does not change the history element that you | 485 you reuse it; this does not change the history element that you |
486 ``moved'' to, but your new argument does go at the end of the history | 486 ``moved'' to, but your new argument does go at the end of the history |
487 list in its own right. | 487 list in its own right. |
488 | 488 |
489 For many minibuffer arguments there is a ``default'' value. In some | 489 For many minibuffer arguments there is a ``default'' value. Then |
490 cases, the minibuffer history commands know the default value. Then you | 490 you can insert the default value into the minibuffer as text by using |
491 can insert the default value into the minibuffer as text by using | 491 @kbd{M-n} to move ``into the future'' in the history. |
492 @kbd{M-n} to move ``into the future'' in the history. Eventually we | |
493 hope to make this feature available whenever the minibuffer has a | |
494 default value. | |
495 | 492 |
496 @findex previous-matching-history-element | 493 @findex previous-matching-history-element |
497 @findex next-matching-history-element | 494 @findex next-matching-history-element |
498 @kindex M-r @r{(minibuffer history)} | 495 @kindex M-r @r{(minibuffer history)} |
499 @kindex M-s @r{(minibuffer history)} | 496 @kindex M-s @r{(minibuffer history)} |