Mercurial > emacs
comparison man/mini.texi @ 25829:ac7e9e5e2ccb
#
author | Dave Love <fx@gnu.org> |
---|---|
date | Wed, 29 Sep 1999 15:17:24 +0000 |
parents | |
children | 99ca9ac9c31a |
comparison
equal
deleted
inserted
replaced
25828:55e4513821f8 | 25829:ac7e9e5e2ccb |
---|---|
1 @c This is part of the Emacs manual. | |
2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 1997 Free Software Foundation, Inc. | |
3 @c See file emacs.texi for copying conditions. | |
4 @node Minibuffer, M-x, Basic, Top | |
5 @chapter The Minibuffer | |
6 @cindex minibuffer | |
7 | |
8 The @dfn{minibuffer} is the facility used by Emacs commands to read | |
9 arguments more complicated than a single number. Minibuffer arguments | |
10 can be file names, buffer names, Lisp function names, Emacs command | |
11 names, Lisp expressions, and many other things, depending on the command | |
12 reading the argument. You can use the usual Emacs editing commands in | |
13 the minibuffer to edit the argument text. | |
14 | |
15 @cindex prompt | |
16 When the minibuffer is in use, it appears in the echo area, and the | |
17 terminal's cursor moves there. The beginning of the minibuffer line | |
18 displays a @dfn{prompt} which says what kind of input you should supply and | |
19 how it will be used. Often this prompt is derived from the name of the | |
20 command that the argument is for. The prompt normally ends with a colon. | |
21 | |
22 @cindex default argument | |
23 Sometimes a @dfn{default argument} appears in parentheses after the | |
24 colon; it too is part of the prompt. The default will be used as the | |
25 argument value if you enter an empty argument (for example, just type | |
26 @key{RET}). For example, commands that read buffer names always show a | |
27 default, which is the name of the buffer that will be used if you type | |
28 just @key{RET}. | |
29 | |
30 The simplest way to enter a minibuffer argument is to type the text | |
31 you want, terminated by @key{RET} which exits the minibuffer. You can | |
32 cancel the command that wants the argument, and get out of the | |
33 minibuffer, by typing @kbd{C-g}. | |
34 | |
35 Since the minibuffer uses the screen space of the echo area, it can | |
36 conflict with other ways Emacs customarily uses the echo area. Here is how | |
37 Emacs handles such conflicts: | |
38 | |
39 @itemize @bullet | |
40 @item | |
41 If a command gets an error while you are in the minibuffer, this does | |
42 not cancel the minibuffer. However, the echo area is needed for the | |
43 error message and therefore the minibuffer itself is hidden for a | |
44 while. It comes back after a few seconds, or as soon as you type | |
45 anything. | |
46 | |
47 @item | |
48 If in the minibuffer you use a command whose purpose is to print a | |
49 message in the echo area, such as @kbd{C-x =}, the message is printed | |
50 normally, and the minibuffer is hidden for a while. It comes back | |
51 after a few seconds, or as soon as you type anything. | |
52 | |
53 @item | |
54 Echoing of keystrokes does not take place while the minibuffer is in | |
55 use. | |
56 @end itemize | |
57 | |
58 @menu | |
59 * File: Minibuffer File. Entering file names with the minibuffer. | |
60 * Edit: Minibuffer Edit. How to edit in the minibuffer. | |
61 * Completion:: An abbreviation facility for minibuffer input. | |
62 * Minibuffer History:: Reusing recent minibuffer arguments. | |
63 * Repetition:: Re-executing commands that used the minibuffer. | |
64 @end menu | |
65 | |
66 @node Minibuffer File | |
67 @section Minibuffers for File Names | |
68 | |
69 Sometimes the minibuffer starts out with text in it. For example, when | |
70 you are supposed to give a file name, the minibuffer starts out containing | |
71 the @dfn{default directory}, which ends with a slash. This is to inform | |
72 you which directory the file will be found in if you do not specify a | |
73 directory. | |
74 | |
75 @c Separate paragraph to clean up ugly pagebreak--rms | |
76 @need 1500 | |
77 For example, the minibuffer might start out with these contents: | |
78 | |
79 @example | |
80 Find File: /u2/emacs/src/ | |
81 @end example | |
82 | |
83 @noindent | |
84 where @samp{Find File:@: } is the prompt. Typing @kbd{buffer.c} | |
85 specifies the file @file{/u2/emacs/src/buffer.c}. To find files in | |
86 nearby directories, use @kbd{..}; thus, if you type | |
87 @kbd{../lisp/simple.el}, you will get the file named | |
88 @file{/u2/emacs/lisp/simple.el}. Alternatively, you can kill with | |
89 @kbd{M-@key{DEL}} the directory names you don't want (@pxref{Words}). | |
90 | |
91 If you don't want any of the default, you can kill it with @kbd{C-a | |
92 C-k}. But you don't need to kill the default; you can simply ignore it. | |
93 Insert an absolute file name, one starting with a slash or a tilde, | |
94 after the default directory. For example, to specify the file | |
95 @file{/etc/termcap}, just insert that name, giving these minibuffer | |
96 contents: | |
97 | |
98 @example | |
99 Find File: /u2/emacs/src//etc/termcap | |
100 @end example | |
101 | |
102 @noindent | |
103 @cindex // in file name | |
104 @cindex double slash in file name | |
105 @cindex slashes repeated in file name | |
106 GNU Emacs gives a special meaning to a double slash (which is not | |
107 normally a useful thing to write): it means, ``ignore everything before | |
108 the second slash in the pair.'' Thus, @samp{/u2/emacs/src/} is ignored | |
109 in the example above, and you get the file @file{/etc/termcap}. | |
110 | |
111 If you set @code{insert-default-directory} to @code{nil}, the default | |
112 directory is not inserted in the minibuffer. This way, the minibuffer | |
113 starts out empty. But the name you type, if relative, is still | |
114 interpreted with respect to the same default directory. | |
115 | |
116 @node Minibuffer Edit | |
117 @section Editing in the Minibuffer | |
118 | |
119 The minibuffer is an Emacs buffer (albeit a peculiar one), and the usual | |
120 Emacs commands are available for editing the text of an argument you are | |
121 entering. | |
122 | |
123 Since @key{RET} in the minibuffer is defined to exit the minibuffer, | |
124 you can't use it to insert a newline in the minibuffer. To do that, | |
125 type @kbd{C-o} or @kbd{C-q C-j}. (Recall that a newline is really the | |
126 character control-J.) | |
127 | |
128 The minibuffer has its own window which always has space on the screen | |
129 but acts as if it were not there when the minibuffer is not in use. When | |
130 the minibuffer is in use, its window is just like the others; you can | |
131 switch to another window with @kbd{C-x o}, edit text in other windows and | |
132 perhaps even visit more files, before returning to the minibuffer to submit | |
133 the argument. You can kill text in another window, return to the | |
134 minibuffer window, and then yank the text to use it in the argument. | |
135 @xref{Windows}. | |
136 | |
137 @findex resize-minibuffer-mode | |
138 @cindex Resize-Minibuffer mode | |
139 @cindex mode, Resize-Minibuffer | |
140 @cindex height of minibuffer | |
141 @cindex size of minibuffer | |
142 @cindex growing minibuffer | |
143 There are some restrictions on the use of the minibuffer window, | |
144 however. You cannot switch buffers in it---the minibuffer and its | |
145 window are permanently attached. Also, you cannot split or kill the | |
146 minibuffer window. But you can make it taller in the normal fashion | |
147 with @kbd{C-x ^}. If you enable Resize-Minibuffer mode, then the | |
148 minibuffer window expands vertically as necessary to hold the text that | |
149 you put in the minibuffer. Use @kbd{M-x resize-minibuffer-mode} to | |
150 enable or disable this minor mode (@pxref{Minor Modes}). | |
151 | |
152 @vindex minibuffer-scroll-overlap | |
153 Scrolling works specially in the minibuffer window. When the | |
154 minibuffer is just one line high, and it contains a long line of text | |
155 that won't fit on the screen, scrolling automatically maintains an | |
156 overlap of a certain number of characters from one continuation line to | |
157 the next. The variable @code{minibuffer-scroll-overlap} specifies how | |
158 many characters of overlap; the default is 20. | |
159 | |
160 If while in the minibuffer you issue a command that displays help text | |
161 of any sort in another window, you can use the @kbd{C-M-v} command while | |
162 in the minibuffer to scroll the help text. This lasts until you exit | |
163 the minibuffer. This feature is especially useful if a completing | |
164 minibuffer gives you a list of possible completions. @xref{Other Window}. | |
165 | |
166 @vindex enable-recursive-minibuffers | |
167 Emacs normally disallows most commands that use the minibuffer while | |
168 the minibuffer is active. This rule is to prevent recursive minibuffers | |
169 from confusing novice users. If you want to be able to use such | |
170 commands in the minibuffer, set the variable | |
171 @code{enable-recursive-minibuffers} to a non-@code{nil} value. | |
172 | |
173 @node Completion | |
174 @section Completion | |
175 @cindex completion | |
176 | |
177 For certain kinds of arguments, you can use @dfn{completion} to enter | |
178 the argument value. Completion means that you type part of the | |
179 argument, then Emacs visibly fills in the rest, or as much as | |
180 can be determined from the part you have typed. | |
181 | |
182 When completion is available, certain keys---@key{TAB}, @key{RET}, and | |
183 @key{SPC}---are rebound to complete the text present in the minibuffer | |
184 into a longer string that it stands for, by matching it against a set of | |
185 @dfn{completion alternatives} provided by the command reading the | |
186 argument. @kbd{?} is defined to display a list of possible completions | |
187 of what you have inserted. | |
188 | |
189 For example, when @kbd{M-x} uses the minibuffer to read the name of a | |
190 command, it provides a list of all available Emacs command names to | |
191 complete against. The completion keys match the text in the minibuffer | |
192 against all the command names, find any additional name characters | |
193 implied by the ones already present in the minibuffer, and add those | |
194 characters to the ones you have given. This is what makes it possible | |
195 to type @kbd{M-x ins @key{SPC} b @key{RET}} instead of @kbd{M-x | |
196 insert-buffer @key{RET}} (for example). | |
197 | |
198 Case is normally significant in completion, because it is significant | |
199 in most of the names that you can complete (buffer names, file names and | |
200 command names). Thus, @samp{fo} does not complete to @samp{Foo}. | |
201 Completion does ignore case distinctions for certain arguments in which | |
202 case does not matter. | |
203 | |
204 @menu | |
205 * Example: Completion Example. | |
206 * Commands: Completion Commands. | |
207 * Strict Completion:: | |
208 * Options: Completion Options. | |
209 @end menu | |
210 | |
211 @node Completion Example | |
212 @subsection Completion Example | |
213 | |
214 @kindex TAB @r{(completion)} | |
215 @findex minibuffer-complete | |
216 A concrete example may help here. If you type @kbd{M-x au @key{TAB}}, | |
217 the @key{TAB} looks for alternatives (in this case, command names) that | |
218 start with @samp{au}. There are several, including | |
219 @code{auto-fill-mode} and @code{auto-save-mode}---but they are all the | |
220 same as far as @code{auto-}, so the @samp{au} in the minibuffer changes | |
221 to @samp{auto-}.@refill | |
222 | |
223 If you type @key{TAB} again immediately, there are multiple | |
224 possibilities for the very next character---it could be any of | |
225 @samp{cfilrs}---so no more characters are added; instead, @key{TAB} | |
226 displays a list of all possible completions in another window. | |
227 | |
228 If you go on to type @kbd{f @key{TAB}}, this @key{TAB} sees | |
229 @samp{auto-f}. The only command name starting this way is | |
230 @code{auto-fill-mode}, so completion fills in the rest of that. You now | |
231 have @samp{auto-fill-mode} in the minibuffer after typing just @kbd{au | |
232 @key{TAB} f @key{TAB}}. Note that @key{TAB} has this effect because in | |
233 the minibuffer it is bound to the command @code{minibuffer-complete} | |
234 when completion is available. | |
235 | |
236 @node Completion Commands | |
237 @subsection Completion Commands | |
238 | |
239 Here is a list of the completion commands defined in the minibuffer | |
240 when completion is available. | |
241 | |
242 @table @kbd | |
243 @item @key{TAB} | |
244 Complete the text in the minibuffer as much as possible | |
245 (@code{minibuffer-complete}). | |
246 @item @key{SPC} | |
247 Complete the minibuffer text, but don't go beyond one word | |
248 (@code{minibuffer-complete-word}). | |
249 @item @key{RET} | |
250 Submit the text in the minibuffer as the argument, possibly completing | |
251 first as described below (@code{minibuffer-complete-and-exit}). | |
252 @item ? | |
253 Print a list of all possible completions of the text in the minibuffer | |
254 (@code{minibuffer-list-completions}). | |
255 @end table | |
256 | |
257 @kindex SPC | |
258 @findex minibuffer-complete-word | |
259 @key{SPC} completes much like @key{TAB}, but never goes beyond the | |
260 next hyphen or space. If you have @samp{auto-f} in the minibuffer and | |
261 type @key{SPC}, it finds that the completion is @samp{auto-fill-mode}, | |
262 but it stops completing after @samp{fill-}. This gives | |
263 @samp{auto-fill-}. Another @key{SPC} at this point completes all the | |
264 way to @samp{auto-fill-mode}. @key{SPC} in the minibuffer when | |
265 completion is available runs the command | |
266 @code{minibuffer-complete-word}. | |
267 | |
268 Here are some commands you can use to choose a completion from a | |
269 window that displays a list of completions: | |
270 | |
271 @table @kbd | |
272 @findex mouse-choose-completion | |
273 @item Mouse-2 | |
274 Clicking mouse button 2 on a completion in the list of possible | |
275 completions chooses that completion (@code{mouse-choose-completion}). | |
276 You normally use this command while point is in the minibuffer; but you | |
277 must click in the list of completions, not in the minibuffer itself. | |
278 | |
279 @findex switch-to-completions | |
280 @item @key{PRIOR} | |
281 @itemx M-v | |
282 Typing @key{PRIOR} or @key{PAGE-UP}, or @kbd{M-v}, while in the | |
283 minibuffer, selects the window showing the completion list buffer | |
284 (@code{switch-to-completions}). This paves the way for using the | |
285 commands below. (Selecting that window in the usual ways has the same | |
286 effect, but this way is more convenient.) | |
287 | |
288 @findex choose-completion | |
289 @item @key{RET} | |
290 Typing @key{RET} @emph{in the completion list buffer} chooses the | |
291 completion that point is in or next to (@code{choose-completion}). To | |
292 use this command, you must first switch windows to the window that shows | |
293 the list of completions. | |
294 | |
295 @findex next-completion | |
296 @item @key{RIGHT} | |
297 Typing the right-arrow key @key{RIGHT} @emph{in the completion list | |
298 buffer} moves point to the following completion (@code{next-completion}). | |
299 | |
300 @findex previous-completion | |
301 @item @key{LEFT} | |
302 Typing the left-arrow key @key{LEFT} @emph{in the completion list | |
303 buffer} moves point toward the beginning of the buffer, to the previous | |
304 completion (@code{previous-completion}). | |
305 @end table | |
306 | |
307 @node Strict Completion | |
308 @subsection Strict Completion | |
309 | |
310 There are three different ways that @key{RET} can work in completing | |
311 minibuffers, depending on how the argument will be used. | |
312 | |
313 @itemize @bullet | |
314 @item | |
315 @dfn{Strict} completion is used when it is meaningless to give any | |
316 argument except one of the known alternatives. For example, when | |
317 @kbd{C-x k} reads the name of a buffer to kill, it is meaningless to | |
318 give anything but the name of an existing buffer. In strict | |
319 completion, @key{RET} refuses to exit if the text in the minibuffer | |
320 does not complete to an exact match. | |
321 | |
322 @item | |
323 @dfn{Cautious} completion is similar to strict completion, except that | |
324 @key{RET} exits only if the text was an exact match already, not | |
325 needing completion. If the text is not an exact match, @key{RET} does | |
326 not exit, but it does complete the text. If it completes to an exact | |
327 match, a second @key{RET} will exit. | |
328 | |
329 Cautious completion is used for reading file names for files that must | |
330 already exist. | |
331 | |
332 @item | |
333 @dfn{Permissive} completion is used when any string whatever is | |
334 meaningful, and the list of completion alternatives is just a guide. | |
335 For example, when @kbd{C-x C-f} reads the name of a file to visit, any | |
336 file name is allowed, in case you want to create a file. In | |
337 permissive completion, @key{RET} takes the text in the minibuffer | |
338 exactly as given, without completing it. | |
339 @end itemize | |
340 | |
341 The completion commands display a list of all possible completions in | |
342 a window whenever there is more than one possibility for the very next | |
343 character. Also, typing @kbd{?} explicitly requests such a list. If | |
344 the list of completions is long, you can scroll it with @kbd{C-M-v} | |
345 (@pxref{Other Window}). | |
346 | |
347 @node Completion Options | |
348 @subsection Completion Options | |
349 | |
350 @vindex completion-ignored-extensions | |
351 When completion is done on file names, certain file names are usually | |
352 ignored. The variable @code{completion-ignored-extensions} contains a | |
353 list of strings; a file whose name ends in any of those strings is | |
354 ignored as a possible completion. The standard value of this variable | |
355 has several elements including @code{".o"}, @code{".elc"}, @code{".dvi"} | |
356 and @code{"~"}. The effect is that, for example, @samp{foo} can | |
357 complete to @samp{foo.c} even though @samp{foo.o} exists as well. | |
358 However, if @emph{all} the possible completions end in ``ignored'' | |
359 strings, then they are not ignored. Ignored extensions do not apply to | |
360 lists of completions---those always mention all possible completions. | |
361 | |
362 @vindex completion-auto-help | |
363 Normally, a completion command that finds the next character is undetermined | |
364 automatically displays a list of all possible completions. If the variable | |
365 @code{completion-auto-help} is set to @code{nil}, this does not happen, | |
366 and you must type @kbd{?} to display the possible completions. | |
367 | |
368 @pindex complete | |
369 The @code{complete} library implements a more powerful kind of | |
370 completion that can complete multiple words at a time. For example, it | |
371 can complete the command name abbreviation @code{p-b} into | |
372 @code{print-buffer}, because no other command starts with two words | |
373 whose initials are @samp{p} and @samp{b}. To use this library, put | |
374 @code{(load "complete")} in your @file{~/.emacs} file (@pxref{Init | |
375 File}). | |
376 | |
377 @cindex Icomplete mode | |
378 Icomplete mode presents a constantly-updated display that tells you | |
379 what completions are available for the text you've entered so far. The | |
380 command to enable or disable this minor mode is @kbd{M-x | |
381 icomplete-mode}. | |
382 | |
383 @node Minibuffer History | |
384 @section Minibuffer History | |
385 @cindex minibuffer history | |
386 @cindex history of minibuffer input | |
387 | |
388 Every argument that you enter with the minibuffer is saved on a | |
389 @dfn{minibuffer history list} so that you can use it again later in | |
390 another argument. Special commands load the text of an earlier argument | |
391 in the minibuffer. They discard the old minibuffer contents, so you can | |
392 think of them as moving through the history of previous arguments. | |
393 | |
394 @table @kbd | |
395 @item @key{UP} | |
396 @itemx M-p | |
397 Move to the next earlier argument string saved in the minibuffer history | |
398 (@code{previous-history-element}). | |
399 @item @key{DOWN} | |
400 @itemx M-n | |
401 Move to the next later argument string saved in the minibuffer history | |
402 (@code{next-history-element}). | |
403 @item M-r @var{regexp} @key{RET} | |
404 Move to an earlier saved argument in the minibuffer history that has a | |
405 match for @var{regexp} (@code{previous-matching-history-element}). | |
406 @item M-s @var{regexp} @key{RET} | |
407 Move to a later saved argument in the minibuffer history that has a | |
408 match for @var{regexp} (@code{next-matching-history-element}). | |
409 @end table | |
410 | |
411 @kindex M-p @r{(minibuffer history)} | |
412 @kindex M-n @r{(minibuffer history)} | |
413 @findex next-history-element | |
414 @findex previous-history-element | |
415 The simplest way to reuse the saved arguments in the history list is | |
416 to move through the history list one element at a time. While in the | |
417 minibuffer, use @kbd{M-p} or up-arrow (@code{previous-history-element}) | |
418 to ``move to'' the next earlier minibuffer input, and use @kbd{M-n} or | |
419 down-arrow (@code{next-history-element}) to ``move to'' the next later | |
420 input. | |
421 | |
422 The previous input that you fetch from the history entirely replaces | |
423 the contents of the minibuffer. To use it as the argument, exit the | |
424 minibuffer as usual with @key{RET}. You can also edit the text before | |
425 you reuse it; this does not change the history element that you | |
426 ``moved'' to, but your new argument does go at the end of the history | |
427 list in its own right. | |
428 | |
429 For many minibuffer arguments there is a ``default'' value. In some | |
430 cases, the minibuffer history commands know the default value. Then you | |
431 can insert the default value into the minibuffer as text by using | |
432 @kbd{M-n} to move ``into the future'' in the history. Eventually we | |
433 hope to make this feature available whenever the minibuffer has a | |
434 default value. | |
435 | |
436 @findex previous-matching-history-element | |
437 @findex next-matching-history-element | |
438 @kindex M-r @r{(minibuffer history)} | |
439 @kindex M-s @r{(minibuffer history)} | |
440 There are also commands to search forward or backward through the | |
441 history; they search for history elements that match a regular | |
442 expression that you specify with the minibuffer. @kbd{M-r} | |
443 (@code{previous-matching-history-element}) searches older elements in | |
444 the history, while @kbd{M-s} (@code{next-matching-history-element}) | |
445 searches newer elements. By special dispensation, these commands can | |
446 use the minibuffer to read their arguments even though you are already | |
447 in the minibuffer when you issue them. As with incremental searching, | |
448 an uppercase letter in the regular expression makes the search | |
449 case-sensitive (@pxref{Search Case}). | |
450 | |
451 @ignore | |
452 We may change the precise way these commands read their arguments. | |
453 Perhaps they will search for a match for the string given so far in the | |
454 minibuffer; perhaps they will search for a literal match rather than a | |
455 regular expression match; perhaps they will only accept matches at the | |
456 beginning of a history element; perhaps they will read the string to | |
457 search for incrementally like @kbd{C-s}. To find out what interface is | |
458 actually available, type @kbd{C-h f previous-matching-history-element}. | |
459 @end ignore | |
460 | |
461 All uses of the minibuffer record your input on a history list, but | |
462 there are separate history lists for different kinds of arguments. For | |
463 example, there is a list for file names, used by all the commands that | |
464 read file names. (As a special feature, this history list records | |
465 the absolute file name, no more and no less, even if that is not how | |
466 you entered the file name.) | |
467 | |
468 There are several other very specific history lists, including one for | |
469 command names read by @kbd{M-x}, one for buffer names, one for arguments | |
470 of commands like @code{query-replace}, and one for compilation commands | |
471 read by @code{compile}. Finally, there is one ``miscellaneous'' history | |
472 list that most minibuffer arguments use. | |
473 | |
474 @vindex history-length | |
475 The variable @code{history-length} specifies the maximum length of a | |
476 minibuffer history list; once a list gets that long, the oldest element | |
477 is deleted each time an element is added. If the value of | |
478 @code{history-length} is @code{t}, though, there is no maximum length | |
479 and elements are never deleted. | |
480 | |
481 @node Repetition | |
482 @section Repeating Minibuffer Commands | |
483 @cindex command history | |
484 @cindex history of commands | |
485 | |
486 Every command that uses the minibuffer at least once is recorded on a | |
487 special history list, together with the values of its arguments, so that | |
488 you can repeat the entire command. In particular, every use of | |
489 @kbd{M-x} is recorded there, since @kbd{M-x} uses the minibuffer to read | |
490 the command name. | |
491 | |
492 @findex list-command-history | |
493 @c widecommands | |
494 @table @kbd | |
495 @item C-x @key{ESC} @key{ESC} | |
496 Re-execute a recent minibuffer command (@code{repeat-complex-command}). | |
497 @item M-x list-command-history | |
498 Display the entire command history, showing all the commands | |
499 @kbd{C-x @key{ESC} @key{ESC}} can repeat, most recent first. | |
500 @end table | |
501 | |
502 @kindex C-x ESC ESC | |
503 @findex repeat-complex-command | |
504 @kbd{C-x @key{ESC} @key{ESC}} is used to re-execute a recent | |
505 minibuffer-using command. With no argument, it repeats the last such | |
506 command. A numeric argument specifies which command to repeat; one | |
507 means the last one, and larger numbers specify earlier ones. | |
508 | |
509 @kbd{C-x @key{ESC} @key{ESC}} works by turning the previous command | |
510 into a Lisp expression and then entering a minibuffer initialized with | |
511 the text for that expression. If you type just @key{RET}, the command | |
512 is repeated as before. You can also change the command by editing the | |
513 Lisp expression. Whatever expression you finally submit is what will be | |
514 executed. The repeated command is added to the front of the command | |
515 history unless it is identical to the most recently executed command | |
516 already there. | |
517 | |
518 Even if you don't understand Lisp syntax, it will probably be obvious | |
519 which command is displayed for repetition. If you do not change the | |
520 text, it will repeat exactly as before. | |
521 | |
522 Once inside the minibuffer for @kbd{C-x @key{ESC} @key{ESC}}, you can | |
523 use the minibuffer history commands (@kbd{M-p}, @kbd{M-n}, @kbd{M-r}, | |
524 @kbd{M-s}; @pxref{Minibuffer History}) to move through the history list | |
525 of saved entire commands. After finding the desired previous command, | |
526 you can edit its expression as usual and then resubmit it by typing | |
527 @key{RET} as usual. | |
528 | |
529 @vindex command-history | |
530 The list of previous minibuffer-using commands is stored as a Lisp | |
531 list in the variable @code{command-history}. Each element is a Lisp | |
532 expression which describes one command and its arguments. Lisp programs | |
533 can re-execute a command by calling @code{eval} with the | |
534 @code{command-history} element. |