176 |
<a name="IDX214"></a> |
<a name="IDX214"></a> |
177 |
<a name="IDX215"></a> |
<a name="IDX215"></a> |
178 |
<p>XEmacs gives a special meaning to a double slash (which is not normally |
<p>XEmacs gives a special meaning to a double slash (which is not normally |
179 |
a useful thing to write): it means, "ignore everything before the |
a useful thing to write): it means, “ignore everything before the |
180 |
second slash in the pair." Thus, <samp>`/u2/emacs/src/'</samp> is ignored in |
second slash in the pair.” Thus, <samp>`/u2/emacs/src/'</samp> is ignored in |
181 |
the example above, and you get the file <tt>`/etc/termcap'</tt>. |
the example above, and you get the file <tt>`/etc/termcap'</tt>. |
182 |
</p> |
</p> |
183 |
<a name="IDX216"></a> |
<a name="IDX216"></a> |
226 |
argument. See section <a href="xemacs_19.html#SEC175">Multiple Windows</a>. |
argument. See section <a href="xemacs_19.html#SEC175">Multiple Windows</a>. |
227 |
</p> |
</p> |
228 |
<p> There are some restrictions on the use of the minibuffer window, |
<p> There are some restrictions on the use of the minibuffer window, |
229 |
however. You cannot switch buffers in it--the minibuffer and its |
however. You cannot switch buffers in it—the minibuffer and its |
230 |
window are permanently attached. Also, you cannot split or kill the |
window are permanently attached. Also, you cannot split or kill the |
231 |
minibuffer window. But you can make it taller in the normal fashion with |
minibuffer window. But you can make it taller in the normal fashion with |
232 |
<kbd>C-x ^</kbd>. If you enable Resize-Minibuffer mode, then the |
<kbd>C-x ^</kbd>. If you enable Resize-Minibuffer mode, then the |
255 |
and get confused. Therefore, most XEmacs commands that use the |
and get confused. Therefore, most XEmacs commands that use the |
256 |
minibuffer refuse to operate if the minibuffer window is selected. If |
minibuffer refuse to operate if the minibuffer window is selected. If |
257 |
the minibuffer is active but you have switched to a different window, |
the minibuffer is active but you have switched to a different window, |
258 |
recursive use of the minibuffer is allowed--if you know enough to try |
recursive use of the minibuffer is allowed—if you know enough to try |
259 |
to do this, you probably will not get confused. |
to do this, you probably will not get confused. |
260 |
</p> |
</p> |
261 |
<a name="IDX219"></a> |
<a name="IDX219"></a> |
288 |
argument, then XEmacs visibly fills in the rest, or as much as |
argument, then XEmacs visibly fills in the rest, or as much as |
289 |
can be determined from the part you have typed. |
can be determined from the part you have typed. |
290 |
</p> |
</p> |
291 |
<p> When completion is available, certain keys--<kbd>TAB</kbd>, <kbd>RET</kbd>, and |
<p> When completion is available, certain keys—<kbd>TAB</kbd>, <kbd>RET</kbd>, and |
292 |
<kbd>SPC</kbd>--are rebound to complete the text present in the |
<kbd>SPC</kbd>—are rebound to complete the text present in the |
293 |
minibuffer into a longer string that it stands for, by matching it |
minibuffer into a longer string that it stands for, by matching it |
294 |
against a set of <em>completion alternatives</em> provided by the command |
against a set of <em>completion alternatives</em> provided by the command |
295 |
reading the argument. <kbd>?</kbd> is defined to display a list of possible |
reading the argument. <kbd>?</kbd> is defined to display a list of possible |
312 |
</p> |
</p> |
313 |
<p>When a completion list is displayed, the completions will highlight as |
<p>When a completion list is displayed, the completions will highlight as |
314 |
you move the mouse over them. Clicking the middle mouse button on any |
you move the mouse over them. Clicking the middle mouse button on any |
315 |
highlighted completion will "select" it just as if you had typed it in |
highlighted completion will “select” it just as if you had typed it in |
316 |
and hit <kbd>RET</kbd>. |
and hit <kbd>RET</kbd>. |
317 |
</p> |
</p> |
318 |
<table class="menu" border="0" cellspacing="0"> |
<table class="menu" border="0" cellspacing="0"> |
350 |
<p> A concrete example may help here. If you type <kbd>M-x au <kbd>TAB</kbd></kbd>, |
<p> A concrete example may help here. If you type <kbd>M-x au <kbd>TAB</kbd></kbd>, |
351 |
the <kbd>TAB</kbd> looks for alternatives (in this case, command names) that |
the <kbd>TAB</kbd> looks for alternatives (in this case, command names) that |
352 |
start with <samp>`au'</samp>. There are several, including |
start with <samp>`au'</samp>. There are several, including |
353 |
<code>auto-fill-mode</code> and <code>auto-save-mode</code>--but they are all the |
<code>auto-fill-mode</code> and <code>auto-save-mode</code>—but they are all the |
354 |
same as far as <code>auto</code>, so the <samp>`au'</samp> in the minibuffer changes |
same as far as <code>auto</code>, so the <samp>`au'</samp> in the minibuffer changes |
355 |
to <samp>`auto'</samp>. |
to <samp>`auto'</samp>. |
356 |
</p> |
</p> |
357 |
<p> If you type <kbd>TAB</kbd> again immediately, there are multiple |
<p> If you type <kbd>TAB</kbd> again immediately, there are multiple |
358 |
possibilities for the very next character--it could be any of |
possibilities for the very next character—it could be any of |
359 |
<samp>`c-'</samp>--so no more characters are added; instead, <kbd>TAB</kbd> |
<samp>`c-'</samp>—so no more characters are added; instead, <kbd>TAB</kbd> |
360 |
displays a list of all possible completions in another window. |
displays a list of all possible completions in another window. |
361 |
</p> |
</p> |
362 |
<p> If you go on to type <kbd>-f <kbd>TAB</kbd></kbd>, this <kbd>TAB</kbd> sees |
<p> If you go on to type <kbd>-f <kbd>TAB</kbd></kbd>, this <kbd>TAB</kbd> sees |
564 |
has several elements including <code>".o"</code>, <code>".elc"</code>, <code>".dvi"</code> |
has several elements including <code>".o"</code>, <code>".elc"</code>, <code>".dvi"</code> |
565 |
and <code>"~"</code>. The effect is that, for example, <samp>`foo'</samp> can |
and <code>"~"</code>. The effect is that, for example, <samp>`foo'</samp> can |
566 |
complete to <samp>`foo.c'</samp> even though <samp>`foo.o'</samp> exists as well. |
complete to <samp>`foo.c'</samp> even though <samp>`foo.o'</samp> exists as well. |
567 |
However, if <em>all</em> the possible completions end in "ignored" |
However, if <em>all</em> the possible completions end in “ignored” |
568 |
strings, then they are not ignored. Ignored extensions do not apply to |
strings, then they are not ignored. Ignored extensions do not apply to |
569 |
lists of completions--those always mention all possible completions. |
lists of completions—those always mention all possible completions. |
570 |
</p> |
</p> |
571 |
<a name="IDX227"></a> |
<a name="IDX227"></a> |
572 |
<p> If a completion command finds the next character is undetermined, it |
<p> If a completion command finds the next character is undetermined, it |
641 |
<p> The simplest way to reuse the saved arguments in the history list is |
<p> The simplest way to reuse the saved arguments in the history list is |
642 |
to move through the history list one element at a time. While in the |
to move through the history list one element at a time. While in the |
643 |
minibuffer, use <kbd>M-p</kbd> or up-arrow (<code>previous-history-element</code>) |
minibuffer, use <kbd>M-p</kbd> or up-arrow (<code>previous-history-element</code>) |
644 |
to "move to" the next earlier minibuffer input, and use <kbd>M-n</kbd> or |
to “move to” the next earlier minibuffer input, and use <kbd>M-n</kbd> or |
645 |
down-arrow (<code>next-history-element</code>) to "move to" the next later |
down-arrow (<code>next-history-element</code>) to “move to” the next later |
646 |
input. |
input. |
647 |
</p> |
</p> |
648 |
<p> The previous input that you fetch from the history entirely replaces |
<p> The previous input that you fetch from the history entirely replaces |
649 |
the contents of the minibuffer. To use it as the argument, exit the |
the contents of the minibuffer. To use it as the argument, exit the |
650 |
minibuffer as usual with <kbd>RET</kbd>. You can also edit the text before |
minibuffer as usual with <kbd>RET</kbd>. You can also edit the text before |
651 |
you reuse it; this does not change the history element that you |
you reuse it; this does not change the history element that you |
652 |
"moved" to, but your new argument does go at the end of the history |
“moved” to, but your new argument does go at the end of the history |
653 |
list in its own right. |
list in its own right. |
654 |
</p> |
</p> |
655 |
<p> For many minibuffer arguments there is a "default" value. In some |
<p> For many minibuffer arguments there is a “default” value. In some |
656 |
cases, the minibuffer history commands know the default value. Then you |
cases, the minibuffer history commands know the default value. Then you |
657 |
can insert the default value into the minibuffer as text by using |
can insert the default value into the minibuffer as text by using |
658 |
<kbd>M-n</kbd> to move "into the future" in the history. |
<kbd>M-n</kbd> to move “into the future” in the history. |
659 |
</p> |
</p> |
660 |
<a name="IDX234"></a> |
<a name="IDX234"></a> |
661 |
<a name="IDX235"></a> |
<a name="IDX235"></a> |
680 |
<p> There are several other very specific history lists, including one for |
<p> There are several other very specific history lists, including one for |
681 |
command names read by <kbd>M-x</kbd>, one for buffer names, one for arguments |
command names read by <kbd>M-x</kbd>, one for buffer names, one for arguments |
682 |
of commands like <code>query-replace</code>, and one for compilation commands |
of commands like <code>query-replace</code>, and one for compilation commands |
683 |
read by <code>compile</code>. Finally, there is one "miscellaneous" history |
read by <code>compile</code>. Finally, there is one “miscellaneous” history |
684 |
list that most minibuffer arguments use. |
list that most minibuffer arguments use. |
685 |
</p> |
</p> |
686 |
|
|