| 1 | @c -*-texinfo-*- |
| 2 | @c This is part of the GNU Emacs Lisp Reference Manual. |
| 3 | @c Copyright (C) 1990-1995, 1998-1999, 2001-2011 |
| 4 | @c Free Software Foundation, Inc. |
| 5 | @c See the file elisp.texi for copying conditions. |
| 6 | @setfilename ../../info/minibuf |
| 7 | @node Minibuffers, Command Loop, Read and Print, Top |
| 8 | @chapter Minibuffers |
| 9 | @cindex arguments, reading |
| 10 | @cindex complex arguments |
| 11 | @cindex minibuffer |
| 12 | |
| 13 | A @dfn{minibuffer} is a special buffer that Emacs commands use to |
| 14 | read arguments more complicated than the single numeric prefix |
| 15 | argument. These arguments include file names, buffer names, and |
| 16 | command names (as in @kbd{M-x}). The minibuffer is displayed on the |
| 17 | bottom line of the frame, in the same place as the echo area |
| 18 | (@pxref{The Echo Area}), but only while it is in use for reading an |
| 19 | argument. |
| 20 | |
| 21 | @menu |
| 22 | * Intro to Minibuffers:: Basic information about minibuffers. |
| 23 | * Text from Minibuffer:: How to read a straight text string. |
| 24 | * Object from Minibuffer:: How to read a Lisp object or expression. |
| 25 | * Minibuffer History:: Recording previous minibuffer inputs |
| 26 | so the user can reuse them. |
| 27 | * Initial Input:: Specifying initial contents for the minibuffer. |
| 28 | * Completion:: How to invoke and customize completion. |
| 29 | * Yes-or-No Queries:: Asking a question with a simple answer. |
| 30 | * Multiple Queries:: Asking a series of similar questions. |
| 31 | * Reading a Password:: Reading a password from the terminal. |
| 32 | * Minibuffer Commands:: Commands used as key bindings in minibuffers. |
| 33 | * Minibuffer Contents:: How such commands access the minibuffer text. |
| 34 | * Minibuffer Windows:: Operating on the special minibuffer windows. |
| 35 | * Recursive Mini:: Whether recursive entry to minibuffer is allowed. |
| 36 | * Minibuffer Misc:: Various customization hooks and variables. |
| 37 | @end menu |
| 38 | |
| 39 | @node Intro to Minibuffers |
| 40 | @section Introduction to Minibuffers |
| 41 | |
| 42 | In most ways, a minibuffer is a normal Emacs buffer. Most operations |
| 43 | @emph{within} a buffer, such as editing commands, work normally in a |
| 44 | minibuffer. However, many operations for managing buffers do not apply |
| 45 | to minibuffers. The name of a minibuffer always has the form @w{@samp{ |
| 46 | *Minibuf-@var{number}*}}, and it cannot be changed. Minibuffers are |
| 47 | displayed only in special windows used only for minibuffers; these |
| 48 | windows always appear at the bottom of a frame. (Sometimes frames have |
| 49 | no minibuffer window, and sometimes a special kind of frame contains |
| 50 | nothing but a minibuffer window; see @ref{Minibuffers and Frames}.) |
| 51 | |
| 52 | The text in the minibuffer always starts with the @dfn{prompt string}, |
| 53 | the text that was specified by the program that is using the minibuffer |
| 54 | to tell the user what sort of input to type. This text is marked |
| 55 | read-only so you won't accidentally delete or change it. It is also |
| 56 | marked as a field (@pxref{Fields}), so that certain motion functions, |
| 57 | including @code{beginning-of-line}, @code{forward-word}, |
| 58 | @code{forward-sentence}, and @code{forward-paragraph}, stop at the |
| 59 | boundary between the prompt and the actual text. |
| 60 | |
| 61 | The minibuffer's window is normally a single line; it grows |
| 62 | automatically if the contents require more space. You can explicitly |
| 63 | resize it temporarily with the window sizing commands; it reverts to |
| 64 | its normal size when the minibuffer is exited. You can resize it |
| 65 | permanently by using the window sizing commands in the frame's other |
| 66 | window, when the minibuffer is not active. If the frame contains just |
| 67 | a minibuffer, you can change the minibuffer's size by changing the |
| 68 | frame's size. |
| 69 | |
| 70 | Use of the minibuffer reads input events, and that alters the values |
| 71 | of variables such as @code{this-command} and @code{last-command} |
| 72 | (@pxref{Command Loop Info}). Your program should bind them around the |
| 73 | code that uses the minibuffer, if you do not want that to change them. |
| 74 | |
| 75 | Under some circumstances, a command can use a minibuffer even if |
| 76 | there is an active minibuffer; such minibuffers are called a |
| 77 | @dfn{recursive minibuffer}. The first minibuffer is named |
| 78 | @w{@samp{ *Minibuf-0*}}. Recursive minibuffers are named by |
| 79 | incrementing the number at the end of the name. (The names begin with |
| 80 | a space so that they won't show up in normal buffer lists.) Of |
| 81 | several recursive minibuffers, the innermost (or most recently |
| 82 | entered) is the active minibuffer. We usually call this ``the'' |
| 83 | minibuffer. You can permit or forbid recursive minibuffers by setting |
| 84 | the variable @code{enable-recursive-minibuffers}, or by putting |
| 85 | properties of that name on command symbols (@xref{Recursive Mini}.) |
| 86 | |
| 87 | Like other buffers, a minibuffer uses a local keymap |
| 88 | (@pxref{Keymaps}) to specify special key bindings. The function that |
| 89 | invokes the minibuffer also sets up its local map according to the job |
| 90 | to be done. @xref{Text from Minibuffer}, for the non-completion |
| 91 | minibuffer local maps. @xref{Completion Commands}, for the minibuffer |
| 92 | local maps for completion. |
| 93 | |
| 94 | When Emacs is running in batch mode, any request to read from the |
| 95 | minibuffer actually reads a line from the standard input descriptor that |
| 96 | was supplied when Emacs was started. |
| 97 | |
| 98 | @node Text from Minibuffer |
| 99 | @section Reading Text Strings with the Minibuffer |
| 100 | |
| 101 | The most basic primitive for minibuffer input is |
| 102 | @code{read-from-minibuffer}, which can be used to read either a string |
| 103 | or a Lisp object in textual form. The function @code{read-regexp} is |
| 104 | used for reading regular expressions (@pxref{Regular Expressions}), |
| 105 | which are a special kind of string. There are also specialized |
| 106 | functions for reading commands, variables, file names, etc.@: |
| 107 | (@pxref{Completion}). |
| 108 | |
| 109 | In most cases, you should not call minibuffer input functions in the |
| 110 | middle of a Lisp function. Instead, do all minibuffer input as part of |
| 111 | reading the arguments for a command, in the @code{interactive} |
| 112 | specification. @xref{Defining Commands}. |
| 113 | |
| 114 | @defun read-from-minibuffer prompt-string &optional initial-contents keymap read hist default inherit-input-method |
| 115 | This function is the most general way to get input from the |
| 116 | minibuffer. By default, it accepts arbitrary text and returns it as a |
| 117 | string; however, if @var{read} is non-@code{nil}, then it uses |
| 118 | @code{read} to convert the text into a Lisp object (@pxref{Input |
| 119 | Functions}). |
| 120 | |
| 121 | The first thing this function does is to activate a minibuffer and |
| 122 | display it with @var{prompt-string} as the prompt. This value must be a |
| 123 | string. Then the user can edit text in the minibuffer. |
| 124 | |
| 125 | When the user types a command to exit the minibuffer, |
| 126 | @code{read-from-minibuffer} constructs the return value from the text in |
| 127 | the minibuffer. Normally it returns a string containing that text. |
| 128 | However, if @var{read} is non-@code{nil}, @code{read-from-minibuffer} |
| 129 | reads the text and returns the resulting Lisp object, unevaluated. |
| 130 | (@xref{Input Functions}, for information about reading.) |
| 131 | |
| 132 | The argument @var{default} specifies default values to make available |
| 133 | through the history commands. It should be a string, a list of |
| 134 | strings, or @code{nil}. The string or strings become the minibuffer's |
| 135 | ``future history,'' available to the user with @kbd{M-n}. |
| 136 | |
| 137 | If @var{read} is non-@code{nil}, then @var{default} is also used |
| 138 | as the input to @code{read}, if the user enters empty input. |
| 139 | If @var{default} is a list of strings, the first string is used as the input. |
| 140 | If @var{default} is @code{nil}, empty input results in an @code{end-of-file} error. |
| 141 | However, in the usual case (where @var{read} is @code{nil}), |
| 142 | @code{read-from-minibuffer} ignores @var{default} when the user enters |
| 143 | empty input and returns an empty string, @code{""}. In this respect, |
| 144 | it differs from all the other minibuffer input functions in this chapter. |
| 145 | |
| 146 | If @var{keymap} is non-@code{nil}, that keymap is the local keymap to |
| 147 | use in the minibuffer. If @var{keymap} is omitted or @code{nil}, the |
| 148 | value of @code{minibuffer-local-map} is used as the keymap. Specifying |
| 149 | a keymap is the most important way to customize the minibuffer for |
| 150 | various applications such as completion. |
| 151 | |
| 152 | The argument @var{hist} specifies which history list variable to use |
| 153 | for saving the input and for history commands used in the minibuffer. |
| 154 | It defaults to @code{minibuffer-history}. @xref{Minibuffer History}. |
| 155 | |
| 156 | If the variable @code{minibuffer-allow-text-properties} is |
| 157 | non-@code{nil}, then the string which is returned includes whatever text |
| 158 | properties were present in the minibuffer. Otherwise all the text |
| 159 | properties are stripped when the value is returned. |
| 160 | |
| 161 | If the argument @var{inherit-input-method} is non-@code{nil}, then the |
| 162 | minibuffer inherits the current input method (@pxref{Input Methods}) and |
| 163 | the setting of @code{enable-multibyte-characters} (@pxref{Text |
| 164 | Representations}) from whichever buffer was current before entering the |
| 165 | minibuffer. |
| 166 | |
| 167 | Use of @var{initial-contents} is mostly deprecated; we recommend using |
| 168 | a non-@code{nil} value only in conjunction with specifying a cons cell |
| 169 | for @var{hist}. @xref{Initial Input}. |
| 170 | @end defun |
| 171 | |
| 172 | @defun read-string prompt &optional initial history default inherit-input-method |
| 173 | This function reads a string from the minibuffer and returns it. The |
| 174 | arguments @var{prompt}, @var{initial}, @var{history} and |
| 175 | @var{inherit-input-method} are used as in @code{read-from-minibuffer}. |
| 176 | The keymap used is @code{minibuffer-local-map}. |
| 177 | |
| 178 | The optional argument @var{default} is used as in |
| 179 | @code{read-from-minibuffer}, except that, if non-@code{nil}, it also |
| 180 | specifies a default value to return if the user enters null input. As |
| 181 | in @code{read-from-minibuffer} it should be a string, a list of |
| 182 | strings, or @code{nil} which is equivalent to an empty string. When |
| 183 | @var{default} is a string, that string is the default value. When it |
| 184 | is a list of strings, the first string is the default value. (All |
| 185 | these strings are available to the user in the ``future minibuffer |
| 186 | history.'') |
| 187 | |
| 188 | This function works by calling the |
| 189 | @code{read-from-minibuffer} function: |
| 190 | |
| 191 | @smallexample |
| 192 | @group |
| 193 | (read-string @var{prompt} @var{initial} @var{history} @var{default} @var{inherit}) |
| 194 | @equiv{} |
| 195 | (let ((value |
| 196 | (read-from-minibuffer @var{prompt} @var{initial} nil nil |
| 197 | @var{history} @var{default} @var{inherit}))) |
| 198 | (if (and (equal value "") @var{default}) |
| 199 | (if (consp @var{default}) (car @var{default}) @var{default}) |
| 200 | value)) |
| 201 | @end group |
| 202 | @end smallexample |
| 203 | @end defun |
| 204 | |
| 205 | @defun read-regexp prompt &optional default-value |
| 206 | This function reads a regular expression as a string from the |
| 207 | minibuffer and returns it. The argument @var{prompt} is used as in |
| 208 | @code{read-from-minibuffer}. The keymap used is |
| 209 | @code{minibuffer-local-map}, and @code{regexp-history} is used as the |
| 210 | history list (@pxref{Minibuffer History, regexp-history}). |
| 211 | |
| 212 | The optional argument @var{default-value} specifies a default value to |
| 213 | return if the user enters null input; it should be a string, or |
| 214 | @code{nil} which is equivalent to an empty string. |
| 215 | |
| 216 | In addition, @code{read-regexp} collects a few useful candidates for |
| 217 | input and passes them to @code{read-from-minibuffer}, to make them |
| 218 | available to the user as the ``future minibuffer history list'' |
| 219 | (@pxref{Minibuffer History, future list,, emacs, The GNU Emacs |
| 220 | Manual}). These candidates are: |
| 221 | |
| 222 | @itemize @minus |
| 223 | @item |
| 224 | The word or symbol at point. |
| 225 | @item |
| 226 | The last regexp used in an incremental search. |
| 227 | @item |
| 228 | The last string used in an incremental search. |
| 229 | @item |
| 230 | The last string or pattern used in query-replace commands. |
| 231 | @end itemize |
| 232 | |
| 233 | This function works by calling the @code{read-from-minibuffer} |
| 234 | function, after computing the list of defaults as described above. |
| 235 | @end defun |
| 236 | |
| 237 | @defvar minibuffer-allow-text-properties |
| 238 | If this variable is @code{nil}, then @code{read-from-minibuffer} strips |
| 239 | all text properties from the minibuffer input before returning it. |
| 240 | This variable also affects @code{read-string}. However, |
| 241 | @code{read-no-blanks-input} (see below), as well as |
| 242 | @code{read-minibuffer} and related functions (@pxref{Object from |
| 243 | Minibuffer,, Reading Lisp Objects With the Minibuffer}), and all |
| 244 | functions that do minibuffer input with completion, discard text |
| 245 | properties unconditionally, regardless of the value of this variable. |
| 246 | @end defvar |
| 247 | |
| 248 | @defvar minibuffer-local-map |
| 249 | This |
| 250 | @anchor{Definition of minibuffer-local-map} |
| 251 | @c avoid page break at anchor; work around Texinfo deficiency |
| 252 | is the default local keymap for reading from the minibuffer. By |
| 253 | default, it makes the following bindings: |
| 254 | |
| 255 | @table @asis |
| 256 | @item @kbd{C-j} |
| 257 | @code{exit-minibuffer} |
| 258 | |
| 259 | @item @key{RET} |
| 260 | @code{exit-minibuffer} |
| 261 | |
| 262 | @item @kbd{C-g} |
| 263 | @code{abort-recursive-edit} |
| 264 | |
| 265 | @item @kbd{M-n} |
| 266 | @itemx @key{DOWN} |
| 267 | @code{next-history-element} |
| 268 | |
| 269 | @item @kbd{M-p} |
| 270 | @itemx @key{UP} |
| 271 | @code{previous-history-element} |
| 272 | |
| 273 | @item @kbd{M-s} |
| 274 | @code{next-matching-history-element} |
| 275 | |
| 276 | @item @kbd{M-r} |
| 277 | @code{previous-matching-history-element} |
| 278 | @end table |
| 279 | @end defvar |
| 280 | |
| 281 | @c In version 18, initial is required |
| 282 | @c Emacs 19 feature |
| 283 | @defun read-no-blanks-input prompt &optional initial inherit-input-method |
| 284 | This function reads a string from the minibuffer, but does not allow |
| 285 | whitespace characters as part of the input: instead, those characters |
| 286 | terminate the input. The arguments @var{prompt}, @var{initial}, and |
| 287 | @var{inherit-input-method} are used as in @code{read-from-minibuffer}. |
| 288 | |
| 289 | This is a simplified interface to the @code{read-from-minibuffer} |
| 290 | function, and passes the value of the @code{minibuffer-local-ns-map} |
| 291 | keymap as the @var{keymap} argument for that function. Since the keymap |
| 292 | @code{minibuffer-local-ns-map} does not rebind @kbd{C-q}, it @emph{is} |
| 293 | possible to put a space into the string, by quoting it. |
| 294 | |
| 295 | This function discards text properties, regardless of the value of |
| 296 | @code{minibuffer-allow-text-properties}. |
| 297 | |
| 298 | @smallexample |
| 299 | @group |
| 300 | (read-no-blanks-input @var{prompt} @var{initial}) |
| 301 | @equiv{} |
| 302 | (let (minibuffer-allow-text-properties) |
| 303 | (read-from-minibuffer @var{prompt} @var{initial} minibuffer-local-ns-map)) |
| 304 | @end group |
| 305 | @end smallexample |
| 306 | @end defun |
| 307 | |
| 308 | @defvar minibuffer-local-ns-map |
| 309 | This built-in variable is the keymap used as the minibuffer local keymap |
| 310 | in the function @code{read-no-blanks-input}. By default, it makes the |
| 311 | following bindings, in addition to those of @code{minibuffer-local-map}: |
| 312 | |
| 313 | @table @asis |
| 314 | @item @key{SPC} |
| 315 | @cindex @key{SPC} in minibuffer |
| 316 | @code{exit-minibuffer} |
| 317 | |
| 318 | @item @key{TAB} |
| 319 | @cindex @key{TAB} in minibuffer |
| 320 | @code{exit-minibuffer} |
| 321 | |
| 322 | @item @kbd{?} |
| 323 | @cindex @kbd{?} in minibuffer |
| 324 | @code{self-insert-and-exit} |
| 325 | @end table |
| 326 | @end defvar |
| 327 | |
| 328 | @node Object from Minibuffer |
| 329 | @section Reading Lisp Objects with the Minibuffer |
| 330 | |
| 331 | This section describes functions for reading Lisp objects with the |
| 332 | minibuffer. |
| 333 | |
| 334 | @defun read-minibuffer prompt &optional initial |
| 335 | This function reads a Lisp object using the minibuffer, and returns it |
| 336 | without evaluating it. The arguments @var{prompt} and @var{initial} are |
| 337 | used as in @code{read-from-minibuffer}. |
| 338 | |
| 339 | This is a simplified interface to the |
| 340 | @code{read-from-minibuffer} function: |
| 341 | |
| 342 | @smallexample |
| 343 | @group |
| 344 | (read-minibuffer @var{prompt} @var{initial}) |
| 345 | @equiv{} |
| 346 | (let (minibuffer-allow-text-properties) |
| 347 | (read-from-minibuffer @var{prompt} @var{initial} nil t)) |
| 348 | @end group |
| 349 | @end smallexample |
| 350 | |
| 351 | Here is an example in which we supply the string @code{"(testing)"} as |
| 352 | initial input: |
| 353 | |
| 354 | @smallexample |
| 355 | @group |
| 356 | (read-minibuffer |
| 357 | "Enter an expression: " (format "%s" '(testing))) |
| 358 | |
| 359 | ;; @r{Here is how the minibuffer is displayed:} |
| 360 | @end group |
| 361 | |
| 362 | @group |
| 363 | ---------- Buffer: Minibuffer ---------- |
| 364 | Enter an expression: (testing)@point{} |
| 365 | ---------- Buffer: Minibuffer ---------- |
| 366 | @end group |
| 367 | @end smallexample |
| 368 | |
| 369 | @noindent |
| 370 | The user can type @key{RET} immediately to use the initial input as a |
| 371 | default, or can edit the input. |
| 372 | @end defun |
| 373 | |
| 374 | @defun eval-minibuffer prompt &optional initial |
| 375 | This function reads a Lisp expression using the minibuffer, evaluates |
| 376 | it, then returns the result. The arguments @var{prompt} and |
| 377 | @var{initial} are used as in @code{read-from-minibuffer}. |
| 378 | |
| 379 | This function simply evaluates the result of a call to |
| 380 | @code{read-minibuffer}: |
| 381 | |
| 382 | @smallexample |
| 383 | @group |
| 384 | (eval-minibuffer @var{prompt} @var{initial}) |
| 385 | @equiv{} |
| 386 | (eval (read-minibuffer @var{prompt} @var{initial})) |
| 387 | @end group |
| 388 | @end smallexample |
| 389 | @end defun |
| 390 | |
| 391 | @defun edit-and-eval-command prompt form |
| 392 | This function reads a Lisp expression in the minibuffer, and then |
| 393 | evaluates it. The difference between this command and |
| 394 | @code{eval-minibuffer} is that here the initial @var{form} is not |
| 395 | optional and it is treated as a Lisp object to be converted to printed |
| 396 | representation rather than as a string of text. It is printed with |
| 397 | @code{prin1}, so if it is a string, double-quote characters (@samp{"}) |
| 398 | appear in the initial text. @xref{Output Functions}. |
| 399 | |
| 400 | The first thing @code{edit-and-eval-command} does is to activate the |
| 401 | minibuffer with @var{prompt} as the prompt. Then it inserts the printed |
| 402 | representation of @var{form} in the minibuffer, and lets the user edit it. |
| 403 | When the user exits the minibuffer, the edited text is read with |
| 404 | @code{read} and then evaluated. The resulting value becomes the value |
| 405 | of @code{edit-and-eval-command}. |
| 406 | |
| 407 | In the following example, we offer the user an expression with initial |
| 408 | text which is a valid form already: |
| 409 | |
| 410 | @smallexample |
| 411 | @group |
| 412 | (edit-and-eval-command "Please edit: " '(forward-word 1)) |
| 413 | |
| 414 | ;; @r{After evaluation of the preceding expression,} |
| 415 | ;; @r{the following appears in the minibuffer:} |
| 416 | @end group |
| 417 | |
| 418 | @group |
| 419 | ---------- Buffer: Minibuffer ---------- |
| 420 | Please edit: (forward-word 1)@point{} |
| 421 | ---------- Buffer: Minibuffer ---------- |
| 422 | @end group |
| 423 | @end smallexample |
| 424 | |
| 425 | @noindent |
| 426 | Typing @key{RET} right away would exit the minibuffer and evaluate the |
| 427 | expression, thus moving point forward one word. |
| 428 | @code{edit-and-eval-command} returns @code{nil} in this example. |
| 429 | @end defun |
| 430 | |
| 431 | @node Minibuffer History |
| 432 | @section Minibuffer History |
| 433 | @cindex minibuffer history |
| 434 | @cindex history list |
| 435 | |
| 436 | A @dfn{minibuffer history list} records previous minibuffer inputs so |
| 437 | the user can reuse them conveniently. A history list is actually a |
| 438 | symbol, not a list; it is a variable whose value is a list of strings |
| 439 | (previous inputs), most recent first. |
| 440 | |
| 441 | There are many separate history lists, used for different kinds of |
| 442 | inputs. It's the Lisp programmer's job to specify the right history |
| 443 | list for each use of the minibuffer. |
| 444 | |
| 445 | You specify the history list with the optional @var{hist} argument |
| 446 | to either @code{read-from-minibuffer} or @code{completing-read}. Here |
| 447 | are the possible values for it: |
| 448 | |
| 449 | @table @asis |
| 450 | @item @var{variable} |
| 451 | Use @var{variable} (a symbol) as the history list. |
| 452 | |
| 453 | @item (@var{variable} . @var{startpos}) |
| 454 | Use @var{variable} (a symbol) as the history list, and assume that the |
| 455 | initial history position is @var{startpos} (a nonnegative integer). |
| 456 | |
| 457 | Specifying 0 for @var{startpos} is equivalent to just specifying the |
| 458 | symbol @var{variable}. @code{previous-history-element} will display |
| 459 | the most recent element of the history list in the minibuffer. If you |
| 460 | specify a positive @var{startpos}, the minibuffer history functions |
| 461 | behave as if @code{(elt @var{variable} (1- @var{STARTPOS}))} were the |
| 462 | history element currently shown in the minibuffer. |
| 463 | |
| 464 | For consistency, you should also specify that element of the history |
| 465 | as the initial minibuffer contents, using the @var{initial} argument |
| 466 | to the minibuffer input function (@pxref{Initial Input}). |
| 467 | @end table |
| 468 | |
| 469 | If you don't specify @var{hist}, then the default history list |
| 470 | @code{minibuffer-history} is used. For other standard history lists, |
| 471 | see below. You can also create your own history list variable; just |
| 472 | initialize it to @code{nil} before the first use. |
| 473 | |
| 474 | Both @code{read-from-minibuffer} and @code{completing-read} add new |
| 475 | elements to the history list automatically, and provide commands to |
| 476 | allow the user to reuse items on the list. The only thing your program |
| 477 | needs to do to use a history list is to initialize it and to pass its |
| 478 | name to the input functions when you wish. But it is safe to modify the |
| 479 | list by hand when the minibuffer input functions are not using it. |
| 480 | |
| 481 | Emacs functions that add a new element to a history list can also |
| 482 | delete old elements if the list gets too long. The variable |
| 483 | @code{history-length} specifies the maximum length for most history |
| 484 | lists. To specify a different maximum length for a particular history |
| 485 | list, put the length in the @code{history-length} property of the |
| 486 | history list symbol. The variable @code{history-delete-duplicates} |
| 487 | specifies whether to delete duplicates in history. |
| 488 | |
| 489 | @defun add-to-history history-var newelt &optional maxelt keep-all |
| 490 | This function adds a new element @var{newelt}, if it isn't the empty |
| 491 | string, to the history list stored in the variable @var{history-var}, |
| 492 | and returns the updated history list. It limits the list length to |
| 493 | the value of @var{maxelt} (if non-@code{nil}) or @code{history-length} |
| 494 | (described below). The possible values of @var{maxelt} have the same |
| 495 | meaning as the values of @code{history-length}. |
| 496 | |
| 497 | Normally, @code{add-to-history} removes duplicate members from the |
| 498 | history list if @code{history-delete-duplicates} is non-@code{nil}. |
| 499 | However, if @var{keep-all} is non-@code{nil}, that says not to remove |
| 500 | duplicates, and to add @var{newelt} to the list even if it is empty. |
| 501 | @end defun |
| 502 | |
| 503 | @defvar history-add-new-input |
| 504 | If the value of this variable is @code{nil}, standard functions that |
| 505 | read from the minibuffer don't add new elements to the history list. |
| 506 | This lets Lisp programs explicitly manage input history by using |
| 507 | @code{add-to-history}. By default, @code{history-add-new-input} is |
| 508 | set to a non-@code{nil} value. |
| 509 | @end defvar |
| 510 | |
| 511 | @defopt history-length |
| 512 | The value of this variable specifies the maximum length for all |
| 513 | history lists that don't specify their own maximum lengths. If the |
| 514 | value is @code{t}, that means there is no maximum (don't delete old |
| 515 | elements). The value of @code{history-length} property of the history |
| 516 | list variable's symbol, if set, overrides this variable for that |
| 517 | particular history list. |
| 518 | @end defopt |
| 519 | |
| 520 | @defopt history-delete-duplicates |
| 521 | If the value of this variable is @code{t}, that means when adding a |
| 522 | new history element, all previous identical elements are deleted. |
| 523 | @end defopt |
| 524 | |
| 525 | Here are some of the standard minibuffer history list variables: |
| 526 | |
| 527 | @defvar minibuffer-history |
| 528 | The default history list for minibuffer history input. |
| 529 | @end defvar |
| 530 | |
| 531 | @defvar query-replace-history |
| 532 | A history list for arguments to @code{query-replace} (and similar |
| 533 | arguments to other commands). |
| 534 | @end defvar |
| 535 | |
| 536 | @defvar file-name-history |
| 537 | A history list for file-name arguments. |
| 538 | @end defvar |
| 539 | |
| 540 | @defvar buffer-name-history |
| 541 | A history list for buffer-name arguments. |
| 542 | @end defvar |
| 543 | |
| 544 | @defvar regexp-history |
| 545 | A history list for regular expression arguments. |
| 546 | @end defvar |
| 547 | |
| 548 | @defvar extended-command-history |
| 549 | A history list for arguments that are names of extended commands. |
| 550 | @end defvar |
| 551 | |
| 552 | @defvar shell-command-history |
| 553 | A history list for arguments that are shell commands. |
| 554 | @end defvar |
| 555 | |
| 556 | @defvar read-expression-history |
| 557 | A history list for arguments that are Lisp expressions to evaluate. |
| 558 | @end defvar |
| 559 | |
| 560 | @node Initial Input |
| 561 | @section Initial Input |
| 562 | |
| 563 | Several of the functions for minibuffer input have an argument called |
| 564 | @var{initial} or @var{initial-contents}. This is a mostly-deprecated |
| 565 | feature for specifying that the minibuffer should start out with |
| 566 | certain text, instead of empty as usual. |
| 567 | |
| 568 | If @var{initial} is a string, the minibuffer starts out containing the |
| 569 | text of the string, with point at the end, when the user starts to |
| 570 | edit the text. If the user simply types @key{RET} to exit the |
| 571 | minibuffer, it will use the initial input string to determine the |
| 572 | value to return. |
| 573 | |
| 574 | @strong{We discourage use of a non-@code{nil} value for |
| 575 | @var{initial}}, because initial input is an intrusive interface. |
| 576 | History lists and default values provide a much more convenient method |
| 577 | to offer useful default inputs to the user. |
| 578 | |
| 579 | There is just one situation where you should specify a string for an |
| 580 | @var{initial} argument. This is when you specify a cons cell for the |
| 581 | @var{hist} or @var{history} argument. @xref{Minibuffer History}. |
| 582 | |
| 583 | @var{initial} can also be a cons cell of the form @code{(@var{string} |
| 584 | . @var{position})}. This means to insert @var{string} in the |
| 585 | minibuffer but put point at @var{position} within the string's text. |
| 586 | |
| 587 | As a historical accident, @var{position} was implemented |
| 588 | inconsistently in different functions. In @code{completing-read}, |
| 589 | @var{position}'s value is interpreted as origin-zero; that is, a value |
| 590 | of 0 means the beginning of the string, 1 means after the first |
| 591 | character, etc. In @code{read-minibuffer}, and the other |
| 592 | non-completion minibuffer input functions that support this argument, |
| 593 | 1 means the beginning of the string 2 means after the first character, |
| 594 | etc. |
| 595 | |
| 596 | Use of a cons cell as the value for @var{initial} arguments is |
| 597 | deprecated in user code. |
| 598 | |
| 599 | @node Completion |
| 600 | @section Completion |
| 601 | @cindex completion |
| 602 | |
| 603 | @dfn{Completion} is a feature that fills in the rest of a name |
| 604 | starting from an abbreviation for it. Completion works by comparing the |
| 605 | user's input against a list of valid names and determining how much of |
| 606 | the name is determined uniquely by what the user has typed. For |
| 607 | example, when you type @kbd{C-x b} (@code{switch-to-buffer}) and then |
| 608 | type the first few letters of the name of the buffer to which you wish |
| 609 | to switch, and then type @key{TAB} (@code{minibuffer-complete}), Emacs |
| 610 | extends the name as far as it can. |
| 611 | |
| 612 | Standard Emacs commands offer completion for names of symbols, files, |
| 613 | buffers, and processes; with the functions in this section, you can |
| 614 | implement completion for other kinds of names. |
| 615 | |
| 616 | The @code{try-completion} function is the basic primitive for |
| 617 | completion: it returns the longest determined completion of a given |
| 618 | initial string, with a given set of strings to match against. |
| 619 | |
| 620 | The function @code{completing-read} provides a higher-level interface |
| 621 | for completion. A call to @code{completing-read} specifies how to |
| 622 | determine the list of valid names. The function then activates the |
| 623 | minibuffer with a local keymap that binds a few keys to commands useful |
| 624 | for completion. Other functions provide convenient simple interfaces |
| 625 | for reading certain kinds of names with completion. |
| 626 | |
| 627 | @menu |
| 628 | * Basic Completion:: Low-level functions for completing strings. |
| 629 | * Minibuffer Completion:: Invoking the minibuffer with completion. |
| 630 | * Completion Commands:: Minibuffer commands that do completion. |
| 631 | * High-Level Completion:: Convenient special cases of completion |
| 632 | (reading buffer name, file name, etc.). |
| 633 | * Reading File Names:: Using completion to read file names and |
| 634 | shell commands. |
| 635 | * Completion Styles:: Specifying rules for performing completion. |
| 636 | * Programmed Completion:: Writing your own completion-function. |
| 637 | @end menu |
| 638 | |
| 639 | @node Basic Completion |
| 640 | @subsection Basic Completion Functions |
| 641 | |
| 642 | The following completion functions have nothing in themselves to do |
| 643 | with minibuffers. We describe them here to keep them near the |
| 644 | higher-level completion features that do use the minibuffer. |
| 645 | |
| 646 | @defun try-completion string collection &optional predicate |
| 647 | This function returns the longest common substring of all possible |
| 648 | completions of @var{string} in @var{collection}. The value of |
| 649 | @var{collection} must be a list of strings or symbols, an alist, an |
| 650 | obarray, a hash table, or a completion function (@pxref{Programmed |
| 651 | Completion}). |
| 652 | |
| 653 | Completion compares @var{string} against each of the permissible |
| 654 | completions specified by @var{collection}. If no permissible |
| 655 | completions match, @code{try-completion} returns @code{nil}. If there |
| 656 | is just one matching completion, and the match is exact, it returns |
| 657 | @code{t}. Otherwise, it returns the longest initial sequence common |
| 658 | to all possible matching completions. |
| 659 | |
| 660 | If @var{collection} is an alist (@pxref{Association Lists}), the |
| 661 | permissible completions are the elements of the alist that are either |
| 662 | strings, symbols, or conses whose @sc{car} is a string or symbol. |
| 663 | Symbols are converted to strings using @code{symbol-name}. Other |
| 664 | elements of the alist are ignored. (Remember that in Emacs Lisp, the |
| 665 | elements of alists do not @emph{have} to be conses.) In particular, a |
| 666 | list of strings or symbols is allowed, even though we usually do not |
| 667 | think of such lists as alists. |
| 668 | |
| 669 | @cindex obarray in completion |
| 670 | If @var{collection} is an obarray (@pxref{Creating Symbols}), the names |
| 671 | of all symbols in the obarray form the set of permissible completions. The |
| 672 | global variable @code{obarray} holds an obarray containing the names of |
| 673 | all interned Lisp symbols. |
| 674 | |
| 675 | Note that the only valid way to make a new obarray is to create it |
| 676 | empty and then add symbols to it one by one using @code{intern}. |
| 677 | Also, you cannot intern a given symbol in more than one obarray. |
| 678 | |
| 679 | If @var{collection} is a hash table, then the keys that are strings |
| 680 | are the possible completions. Other keys are ignored. |
| 681 | |
| 682 | You can also use a symbol that is a function as @var{collection}. |
| 683 | Then the function is solely responsible for performing completion; |
| 684 | @code{try-completion} returns whatever this function returns. The |
| 685 | function is called with three arguments: @var{string}, @var{predicate} |
| 686 | and @code{nil} (the reason for the third argument is so that the same |
| 687 | function can be used in @code{all-completions} and do the appropriate |
| 688 | thing in either case). @xref{Programmed Completion}. |
| 689 | |
| 690 | If the argument @var{predicate} is non-@code{nil}, then it must be a |
| 691 | function of one argument, unless @var{collection} is a hash table, in |
| 692 | which case it should be a function of two arguments. It is used to |
| 693 | test each possible match, and the match is accepted only if |
| 694 | @var{predicate} returns non-@code{nil}. The argument given to |
| 695 | @var{predicate} is either a string or a cons cell (the @sc{car} of |
| 696 | which is a string) from the alist, or a symbol (@emph{not} a symbol |
| 697 | name) from the obarray. If @var{collection} is a hash table, |
| 698 | @var{predicate} is called with two arguments, the string key and the |
| 699 | associated value. |
| 700 | |
| 701 | In addition, to be acceptable, a completion must also match all the |
| 702 | regular expressions in @code{completion-regexp-list}. (Unless |
| 703 | @var{collection} is a function, in which case that function has to |
| 704 | handle @code{completion-regexp-list} itself.) |
| 705 | |
| 706 | In the first of the following examples, the string @samp{foo} is |
| 707 | matched by three of the alist @sc{car}s. All of the matches begin with |
| 708 | the characters @samp{fooba}, so that is the result. In the second |
| 709 | example, there is only one possible match, and it is exact, so the value |
| 710 | is @code{t}. |
| 711 | |
| 712 | @smallexample |
| 713 | @group |
| 714 | (try-completion |
| 715 | "foo" |
| 716 | '(("foobar1" 1) ("barfoo" 2) ("foobaz" 3) ("foobar2" 4))) |
| 717 | @result{} "fooba" |
| 718 | @end group |
| 719 | |
| 720 | @group |
| 721 | (try-completion "foo" '(("barfoo" 2) ("foo" 3))) |
| 722 | @result{} t |
| 723 | @end group |
| 724 | @end smallexample |
| 725 | |
| 726 | In the following example, numerous symbols begin with the characters |
| 727 | @samp{forw}, and all of them begin with the word @samp{forward}. In |
| 728 | most of the symbols, this is followed with a @samp{-}, but not in all, |
| 729 | so no more than @samp{forward} can be completed. |
| 730 | |
| 731 | @smallexample |
| 732 | @group |
| 733 | (try-completion "forw" obarray) |
| 734 | @result{} "forward" |
| 735 | @end group |
| 736 | @end smallexample |
| 737 | |
| 738 | Finally, in the following example, only two of the three possible |
| 739 | matches pass the predicate @code{test} (the string @samp{foobaz} is |
| 740 | too short). Both of those begin with the string @samp{foobar}. |
| 741 | |
| 742 | @smallexample |
| 743 | @group |
| 744 | (defun test (s) |
| 745 | (> (length (car s)) 6)) |
| 746 | @result{} test |
| 747 | @end group |
| 748 | @group |
| 749 | (try-completion |
| 750 | "foo" |
| 751 | '(("foobar1" 1) ("barfoo" 2) ("foobaz" 3) ("foobar2" 4)) |
| 752 | 'test) |
| 753 | @result{} "foobar" |
| 754 | @end group |
| 755 | @end smallexample |
| 756 | @end defun |
| 757 | |
| 758 | @defun all-completions string collection &optional predicate nospace |
| 759 | This function returns a list of all possible completions of |
| 760 | @var{string}. The arguments to this function (aside from |
| 761 | @var{nospace}) are the same as those of @code{try-completion}. Also, |
| 762 | this function uses @code{completion-regexp-list} in the same way that |
| 763 | @code{try-completion} does. |
| 764 | |
| 765 | The optional argument @var{nospace} is obsolete. If it is |
| 766 | non-@code{nil}, completions that start with a space are ignored unless |
| 767 | @var{string} starts with a space. |
| 768 | |
| 769 | If @var{collection} is a function, it is called with three arguments: |
| 770 | @var{string}, @var{predicate} and @code{t}; then @code{all-completions} |
| 771 | returns whatever the function returns. @xref{Programmed Completion}. |
| 772 | |
| 773 | Here is an example, using the function @code{test} shown in the |
| 774 | example for @code{try-completion}: |
| 775 | |
| 776 | @smallexample |
| 777 | @group |
| 778 | (defun test (s) |
| 779 | (> (length (car s)) 6)) |
| 780 | @result{} test |
| 781 | @end group |
| 782 | |
| 783 | @group |
| 784 | (all-completions |
| 785 | "foo" |
| 786 | '(("foobar1" 1) ("barfoo" 2) ("foobaz" 3) ("foobar2" 4)) |
| 787 | 'test) |
| 788 | @result{} ("foobar1" "foobar2") |
| 789 | @end group |
| 790 | @end smallexample |
| 791 | @end defun |
| 792 | |
| 793 | @defun test-completion string collection &optional predicate |
| 794 | @anchor{Definition of test-completion} |
| 795 | This function returns non-@code{nil} if @var{string} is a valid |
| 796 | completion possibility specified by @var{collection} and |
| 797 | @var{predicate}. The arguments are the same as in |
| 798 | @code{try-completion}. For instance, if @var{collection} is a list of |
| 799 | strings, this is true if @var{string} appears in the list and |
| 800 | @var{predicate} is satisfied. |
| 801 | |
| 802 | This function uses @code{completion-regexp-list} in the same |
| 803 | way that @code{try-completion} does. |
| 804 | |
| 805 | If @var{predicate} is non-@code{nil} and if @var{collection} contains |
| 806 | several strings that are equal to each other, as determined by |
| 807 | @code{compare-strings} according to @code{completion-ignore-case}, |
| 808 | then @var{predicate} should accept either all or none of them. |
| 809 | Otherwise, the return value of @code{test-completion} is essentially |
| 810 | unpredictable. |
| 811 | |
| 812 | If @var{collection} is a function, it is called with three arguments, |
| 813 | the values @var{string}, @var{predicate} and @code{lambda}; whatever |
| 814 | it returns, @code{test-completion} returns in turn. |
| 815 | @end defun |
| 816 | |
| 817 | @defun completion-boundaries string collection predicate suffix |
| 818 | This function returns the boundaries of the field on which @var{collection} |
| 819 | will operate, assuming that @var{string} holds the text before point |
| 820 | and @var{suffix} holds the text after point. |
| 821 | |
| 822 | Normally completion operates on the whole string, so for all normal |
| 823 | collections, this will always return @code{(0 . (length |
| 824 | @var{suffix}))}. But more complex completion such as completion on |
| 825 | files is done one field at a time. For example, completion of |
| 826 | @code{"/usr/sh"} will include @code{"/usr/share/"} but not |
| 827 | @code{"/usr/share/doc"} even if @code{"/usr/share/doc"} exists. |
| 828 | Also @code{all-completions} on @code{"/usr/sh"} will not include |
| 829 | @code{"/usr/share/"} but only @code{"share/"}. So if @var{string} is |
| 830 | @code{"/usr/sh"} and @var{suffix} is @code{"e/doc"}, |
| 831 | @code{completion-boundaries} will return @code{(5 . 1)} which tells us |
| 832 | that the @var{collection} will only return completion information that |
| 833 | pertains to the area after @code{"/usr/"} and before @code{"/doc"}. |
| 834 | @end defun |
| 835 | |
| 836 | If you store a completion alist in a variable, you should mark the |
| 837 | variable as ``risky'' with a non-@code{nil} |
| 838 | @code{risky-local-variable} property. @xref{File Local Variables}. |
| 839 | |
| 840 | @defvar completion-ignore-case |
| 841 | If the value of this variable is non-@code{nil}, Emacs does not |
| 842 | consider case significant in completion. Note, however, that this |
| 843 | variable is overridden by @code{read-file-name-completion-ignore-case} |
| 844 | within @code{read-file-name} (@pxref{Reading File Names}), and by |
| 845 | @code{read-buffer-completion-ignore-case} within @code{read-buffer} |
| 846 | (@pxref{High-Level Completion}). |
| 847 | @end defvar |
| 848 | |
| 849 | @defvar completion-regexp-list |
| 850 | This is a list of regular expressions. The completion functions only |
| 851 | consider a completion acceptable if it matches all regular expressions |
| 852 | in this list, with @code{case-fold-search} (@pxref{Searching and Case}) |
| 853 | bound to the value of @code{completion-ignore-case}. |
| 854 | @end defvar |
| 855 | |
| 856 | @defmac lazy-completion-table var fun |
| 857 | This macro provides a way to initialize the variable @var{var} as a |
| 858 | collection for completion in a lazy way, not computing its actual |
| 859 | contents until they are first needed. You use this macro to produce a |
| 860 | value that you store in @var{var}. The actual computation of the |
| 861 | proper value is done the first time you do completion using @var{var}. |
| 862 | It is done by calling @var{fun} with no arguments. The |
| 863 | value @var{fun} returns becomes the permanent value of @var{var}. |
| 864 | |
| 865 | Here is an example of use: |
| 866 | |
| 867 | @smallexample |
| 868 | (defvar foo (lazy-completion-table foo make-my-alist)) |
| 869 | @end smallexample |
| 870 | @end defmac |
| 871 | |
| 872 | The function @code{completion-in-region} provides a convenient way to |
| 873 | perform completion on an arbitrary stretch of text in an Emacs buffer: |
| 874 | |
| 875 | @defun completion-in-region start end collection &optional predicate |
| 876 | This function completes the text in the current buffer between the |
| 877 | positions @var{start} and @var{end}, using @var{collection}. The |
| 878 | argument @var{collection} has the same meaning as in |
| 879 | @code{try-completion} (@pxref{Basic Completion}). |
| 880 | |
| 881 | This function inserts the completion text directly into the current |
| 882 | buffer. Unlike @code{completing-read} (@pxref{Minibuffer |
| 883 | Completion}), it does not activate the minibuffer. |
| 884 | |
| 885 | For this function to work, point must be somewhere between @var{start} |
| 886 | and @var{end}. |
| 887 | @end defun |
| 888 | |
| 889 | @node Minibuffer Completion |
| 890 | @subsection Completion and the Minibuffer |
| 891 | @cindex minibuffer completion |
| 892 | @cindex reading from minibuffer with completion |
| 893 | |
| 894 | This section describes the basic interface for reading from the |
| 895 | minibuffer with completion. |
| 896 | |
| 897 | @defun completing-read prompt collection &optional predicate require-match initial hist default inherit-input-method |
| 898 | This function reads a string in the minibuffer, assisting the user by |
| 899 | providing completion. It activates the minibuffer with prompt |
| 900 | @var{prompt}, which must be a string. |
| 901 | |
| 902 | The actual completion is done by passing @var{collection} and |
| 903 | @var{predicate} to the function @code{try-completion} (@pxref{Basic |
| 904 | Completion}). This happens in certain commands bound in the local |
| 905 | keymaps used for completion. Some of these commands also call |
| 906 | @code{test-completion}. Thus, if @var{predicate} is non-@code{nil}, |
| 907 | it should be compatible with @var{collection} and |
| 908 | @code{completion-ignore-case}. @xref{Definition of test-completion}. |
| 909 | |
| 910 | The value of the optional argument @var{require-match} determines how |
| 911 | the user may exit the minibuffer: |
| 912 | |
| 913 | @itemize @bullet |
| 914 | @item |
| 915 | If @code{nil}, the usual minibuffer exit commands work regardless of |
| 916 | the input in the minibuffer. |
| 917 | |
| 918 | @item |
| 919 | If @code{t}, the usual minibuffer exit commands won't exit unless the |
| 920 | input completes to an element of @var{collection}. |
| 921 | |
| 922 | @item |
| 923 | If @code{confirm}, the user can exit with any input, but is asked for |
| 924 | confirmation if the input is not an element of @var{collection}. |
| 925 | |
| 926 | @item |
| 927 | If @code{confirm-after-completion}, the user can exit with any input, |
| 928 | but is asked for confirmation if the preceding command was a |
| 929 | completion command (i.e., one of the commands in |
| 930 | @code{minibuffer-confirm-exit-commands}) and the resulting input is |
| 931 | not an element of @var{collection}. @xref{Completion Commands}. |
| 932 | |
| 933 | @item |
| 934 | Any other value of @var{require-match} behaves like @code{t}, except |
| 935 | that the exit commands won't exit if it performs completion. |
| 936 | @end itemize |
| 937 | |
| 938 | However, empty input is always permitted, regardless of the value of |
| 939 | @var{require-match}; in that case, @code{completing-read} returns the |
| 940 | first element of @var{default}, if it is a list; @code{""}, if |
| 941 | @var{default} is @code{nil}; or @var{default}. The string or strings |
| 942 | in @var{default} are also available to the user through the history |
| 943 | commands. |
| 944 | |
| 945 | The function @code{completing-read} uses |
| 946 | @code{minibuffer-local-completion-map} as the keymap if |
| 947 | @var{require-match} is @code{nil}, and uses |
| 948 | @code{minibuffer-local-must-match-map} if @var{require-match} is |
| 949 | non-@code{nil}. @xref{Completion Commands}. |
| 950 | |
| 951 | The argument @var{hist} specifies which history list variable to use for |
| 952 | saving the input and for minibuffer history commands. It defaults to |
| 953 | @code{minibuffer-history}. @xref{Minibuffer History}. |
| 954 | |
| 955 | The argument @var{initial} is mostly deprecated; we recommend using a |
| 956 | non-@code{nil} value only in conjunction with specifying a cons cell |
| 957 | for @var{hist}. @xref{Initial Input}. For default input, use |
| 958 | @var{default} instead. |
| 959 | |
| 960 | If the argument @var{inherit-input-method} is non-@code{nil}, then the |
| 961 | minibuffer inherits the current input method (@pxref{Input |
| 962 | Methods}) and the setting of @code{enable-multibyte-characters} |
| 963 | (@pxref{Text Representations}) from whichever buffer was current before |
| 964 | entering the minibuffer. |
| 965 | |
| 966 | If the built-in variable @code{completion-ignore-case} is |
| 967 | non-@code{nil}, completion ignores case when comparing the input |
| 968 | against the possible matches. @xref{Basic Completion}. In this mode |
| 969 | of operation, @var{predicate} must also ignore case, or you will get |
| 970 | surprising results. |
| 971 | |
| 972 | Here's an example of using @code{completing-read}: |
| 973 | |
| 974 | @smallexample |
| 975 | @group |
| 976 | (completing-read |
| 977 | "Complete a foo: " |
| 978 | '(("foobar1" 1) ("barfoo" 2) ("foobaz" 3) ("foobar2" 4)) |
| 979 | nil t "fo") |
| 980 | @end group |
| 981 | |
| 982 | @group |
| 983 | ;; @r{After evaluation of the preceding expression,} |
| 984 | ;; @r{the following appears in the minibuffer:} |
| 985 | |
| 986 | ---------- Buffer: Minibuffer ---------- |
| 987 | Complete a foo: fo@point{} |
| 988 | ---------- Buffer: Minibuffer ---------- |
| 989 | @end group |
| 990 | @end smallexample |
| 991 | |
| 992 | @noindent |
| 993 | If the user then types @kbd{@key{DEL} @key{DEL} b @key{RET}}, |
| 994 | @code{completing-read} returns @code{barfoo}. |
| 995 | |
| 996 | The @code{completing-read} function binds variables to pass |
| 997 | information to the commands that actually do completion. |
| 998 | They are described in the following section. |
| 999 | @end defun |
| 1000 | |
| 1001 | @node Completion Commands |
| 1002 | @subsection Minibuffer Commands that Do Completion |
| 1003 | |
| 1004 | This section describes the keymaps, commands and user options used |
| 1005 | in the minibuffer to do completion. |
| 1006 | |
| 1007 | @defvar minibuffer-completion-table |
| 1008 | The value of this variable is the collection used for completion in |
| 1009 | the minibuffer. This is the global variable that contains what |
| 1010 | @code{completing-read} passes to @code{try-completion}. It is used by |
| 1011 | minibuffer completion commands such as @code{minibuffer-complete-word}. |
| 1012 | @end defvar |
| 1013 | |
| 1014 | @defvar minibuffer-completion-predicate |
| 1015 | This variable's value is the predicate that @code{completing-read} |
| 1016 | passes to @code{try-completion}. The variable is also used by the other |
| 1017 | minibuffer completion functions. |
| 1018 | @end defvar |
| 1019 | |
| 1020 | @defvar minibuffer-completion-confirm |
| 1021 | This variable determines whether Emacs asks for confirmation before |
| 1022 | exiting the minibuffer; @code{completing-read} binds this variable, |
| 1023 | and the function @code{minibuffer-complete-and-exit} checks the value |
| 1024 | before exiting. If the value is @code{nil}, confirmation is not |
| 1025 | required. If the value is @code{confirm}, the user may exit with an |
| 1026 | input that is not a valid completion alternative, but Emacs asks for |
| 1027 | confirmation. If the value is @code{confirm-after-completion}, the |
| 1028 | user may exit with an input that is not a valid completion |
| 1029 | alternative, but Emacs asks for confirmation if the user submitted the |
| 1030 | input right after any of the completion commands in |
| 1031 | @code{minibuffer-confirm-exit-commands}. |
| 1032 | @end defvar |
| 1033 | |
| 1034 | @defvar minibuffer-confirm-exit-commands |
| 1035 | This variable holds a list of commands that cause Emacs to ask for |
| 1036 | confirmation before exiting the minibuffer, if the @var{require-match} |
| 1037 | argument to @code{completing-read} is @code{confirm-after-completion}. |
| 1038 | The confirmation is requested if the user attempts to exit the |
| 1039 | minibuffer immediately after calling any command in this list. |
| 1040 | @end defvar |
| 1041 | |
| 1042 | @deffn Command minibuffer-complete-word |
| 1043 | This function completes the minibuffer contents by at most a single |
| 1044 | word. Even if the minibuffer contents have only one completion, |
| 1045 | @code{minibuffer-complete-word} does not add any characters beyond the |
| 1046 | first character that is not a word constituent. @xref{Syntax Tables}. |
| 1047 | @end deffn |
| 1048 | |
| 1049 | @deffn Command minibuffer-complete |
| 1050 | This function completes the minibuffer contents as far as possible. |
| 1051 | @end deffn |
| 1052 | |
| 1053 | @deffn Command minibuffer-complete-and-exit |
| 1054 | This function completes the minibuffer contents, and exits if |
| 1055 | confirmation is not required, i.e., if |
| 1056 | @code{minibuffer-completion-confirm} is @code{nil}. If confirmation |
| 1057 | @emph{is} required, it is given by repeating this command |
| 1058 | immediately---the command is programmed to work without confirmation |
| 1059 | when run twice in succession. |
| 1060 | @end deffn |
| 1061 | |
| 1062 | @deffn Command minibuffer-completion-help |
| 1063 | This function creates a list of the possible completions of the |
| 1064 | current minibuffer contents. It works by calling @code{all-completions} |
| 1065 | using the value of the variable @code{minibuffer-completion-table} as |
| 1066 | the @var{collection} argument, and the value of |
| 1067 | @code{minibuffer-completion-predicate} as the @var{predicate} argument. |
| 1068 | The list of completions is displayed as text in a buffer named |
| 1069 | @samp{*Completions*}. |
| 1070 | @end deffn |
| 1071 | |
| 1072 | @defun display-completion-list completions &optional common-substring |
| 1073 | This function displays @var{completions} to the stream in |
| 1074 | @code{standard-output}, usually a buffer. (@xref{Read and Print}, for more |
| 1075 | information about streams.) The argument @var{completions} is normally |
| 1076 | a list of completions just returned by @code{all-completions}, but it |
| 1077 | does not have to be. Each element may be a symbol or a string, either |
| 1078 | of which is simply printed. It can also be a list of two strings, |
| 1079 | which is printed as if the strings were concatenated. The first of |
| 1080 | the two strings is the actual completion, the second string serves as |
| 1081 | annotation. |
| 1082 | |
| 1083 | The argument @var{common-substring} is the prefix that is common to |
| 1084 | all the completions. With normal Emacs completion, it is usually the |
| 1085 | same as the string that was completed. @code{display-completion-list} |
| 1086 | uses this to highlight text in the completion list for better visual |
| 1087 | feedback. This is not needed in the minibuffer; for minibuffer |
| 1088 | completion, you can pass @code{nil}. |
| 1089 | |
| 1090 | This function is called by @code{minibuffer-completion-help}. The |
| 1091 | most common way to use it is together with |
| 1092 | @code{with-output-to-temp-buffer}, like this: |
| 1093 | |
| 1094 | @example |
| 1095 | (with-output-to-temp-buffer "*Completions*" |
| 1096 | (display-completion-list |
| 1097 | (all-completions (buffer-string) my-alist) |
| 1098 | (buffer-string))) |
| 1099 | @end example |
| 1100 | @end defun |
| 1101 | |
| 1102 | @defopt completion-auto-help |
| 1103 | If this variable is non-@code{nil}, the completion commands |
| 1104 | automatically display a list of possible completions whenever nothing |
| 1105 | can be completed because the next character is not uniquely determined. |
| 1106 | @end defopt |
| 1107 | |
| 1108 | @defvar minibuffer-local-completion-map |
| 1109 | @code{completing-read} uses this value as the local keymap when an |
| 1110 | exact match of one of the completions is not required. By default, this |
| 1111 | keymap makes the following bindings: |
| 1112 | |
| 1113 | @table @asis |
| 1114 | @item @kbd{?} |
| 1115 | @code{minibuffer-completion-help} |
| 1116 | |
| 1117 | @item @key{SPC} |
| 1118 | @code{minibuffer-complete-word} |
| 1119 | |
| 1120 | @item @key{TAB} |
| 1121 | @code{minibuffer-complete} |
| 1122 | @end table |
| 1123 | |
| 1124 | @noindent |
| 1125 | with other characters bound as in @code{minibuffer-local-map} |
| 1126 | (@pxref{Definition of minibuffer-local-map}). |
| 1127 | @end defvar |
| 1128 | |
| 1129 | @defvar minibuffer-local-must-match-map |
| 1130 | @code{completing-read} uses this value as the local keymap when an |
| 1131 | exact match of one of the completions is required. Therefore, no keys |
| 1132 | are bound to @code{exit-minibuffer}, the command that exits the |
| 1133 | minibuffer unconditionally. By default, this keymap makes the following |
| 1134 | bindings: |
| 1135 | |
| 1136 | @table @asis |
| 1137 | @item @kbd{?} |
| 1138 | @code{minibuffer-completion-help} |
| 1139 | |
| 1140 | @item @key{SPC} |
| 1141 | @code{minibuffer-complete-word} |
| 1142 | |
| 1143 | @item @key{TAB} |
| 1144 | @code{minibuffer-complete} |
| 1145 | |
| 1146 | @item @kbd{C-j} |
| 1147 | @code{minibuffer-complete-and-exit} |
| 1148 | |
| 1149 | @item @key{RET} |
| 1150 | @code{minibuffer-complete-and-exit} |
| 1151 | @end table |
| 1152 | |
| 1153 | @noindent |
| 1154 | with other characters bound as in @code{minibuffer-local-map}. |
| 1155 | @end defvar |
| 1156 | |
| 1157 | @defvar minibuffer-local-filename-completion-map |
| 1158 | This is like @code{minibuffer-local-completion-map} |
| 1159 | except that it does not bind @key{SPC}. This keymap is used by the |
| 1160 | function @code{read-file-name}. |
| 1161 | @end defvar |
| 1162 | |
| 1163 | @defvar minibuffer-local-filename-must-match-map |
| 1164 | This is like @code{minibuffer-local-must-match-map} |
| 1165 | except that it does not bind @key{SPC}. This keymap is used by the |
| 1166 | function @code{read-file-name}. |
| 1167 | @end defvar |
| 1168 | |
| 1169 | @node High-Level Completion |
| 1170 | @subsection High-Level Completion Functions |
| 1171 | |
| 1172 | This section describes the higher-level convenient functions for |
| 1173 | reading certain sorts of names with completion. |
| 1174 | |
| 1175 | In most cases, you should not call these functions in the middle of a |
| 1176 | Lisp function. When possible, do all minibuffer input as part of |
| 1177 | reading the arguments for a command, in the @code{interactive} |
| 1178 | specification. @xref{Defining Commands}. |
| 1179 | |
| 1180 | @defun read-buffer prompt &optional default require-match |
| 1181 | This function reads the name of a buffer and returns it as a string. |
| 1182 | The argument @var{default} is the default name to use, the value to |
| 1183 | return if the user exits with an empty minibuffer. If non-@code{nil}, |
| 1184 | it should be a string, a list of strings, or a buffer. If it is |
| 1185 | a list, the default value is the first element of this list. It is |
| 1186 | mentioned in the prompt, but is not inserted in the minibuffer as |
| 1187 | initial input. |
| 1188 | |
| 1189 | The argument @var{prompt} should be a string ending with a colon and a |
| 1190 | space. If @var{default} is non-@code{nil}, the function inserts it in |
| 1191 | @var{prompt} before the colon to follow the convention for reading from |
| 1192 | the minibuffer with a default value (@pxref{Programming Tips}). |
| 1193 | |
| 1194 | The optional argument @var{require-match} has the same meaning as in |
| 1195 | @code{completing-read}. @xref{Minibuffer Completion}. |
| 1196 | |
| 1197 | In the following example, the user enters @samp{minibuffer.t}, and |
| 1198 | then types @key{RET}. The argument @var{require-match} is @code{t}, |
| 1199 | and the only buffer name starting with the given input is |
| 1200 | @samp{minibuffer.texi}, so that name is the value. |
| 1201 | |
| 1202 | @example |
| 1203 | (read-buffer "Buffer name: " "foo" t) |
| 1204 | @group |
| 1205 | ;; @r{After evaluation of the preceding expression,} |
| 1206 | ;; @r{the following prompt appears,} |
| 1207 | ;; @r{with an empty minibuffer:} |
| 1208 | @end group |
| 1209 | |
| 1210 | @group |
| 1211 | ---------- Buffer: Minibuffer ---------- |
| 1212 | Buffer name (default foo): @point{} |
| 1213 | ---------- Buffer: Minibuffer ---------- |
| 1214 | @end group |
| 1215 | |
| 1216 | @group |
| 1217 | ;; @r{The user types @kbd{minibuffer.t @key{RET}}.} |
| 1218 | @result{} "minibuffer.texi" |
| 1219 | @end group |
| 1220 | @end example |
| 1221 | @end defun |
| 1222 | |
| 1223 | @defopt read-buffer-function |
| 1224 | This variable specifies how to read buffer names. The function is |
| 1225 | called with the arguments passed to @code{read-buffer}. For example, |
| 1226 | if you set this variable to @code{iswitchb-read-buffer}, all Emacs |
| 1227 | commands that call @code{read-buffer} to read a buffer name will |
| 1228 | actually use the @code{iswitchb} package to read it. |
| 1229 | @end defopt |
| 1230 | |
| 1231 | @defopt read-buffer-completion-ignore-case |
| 1232 | If this variable is non-@code{nil}, @code{read-buffer} ignores case |
| 1233 | when performing completion. |
| 1234 | @end defopt |
| 1235 | |
| 1236 | @defun read-command prompt &optional default |
| 1237 | This function reads the name of a command and returns it as a Lisp |
| 1238 | symbol. The argument @var{prompt} is used as in |
| 1239 | @code{read-from-minibuffer}. Recall that a command is anything for |
| 1240 | which @code{commandp} returns @code{t}, and a command name is a symbol |
| 1241 | for which @code{commandp} returns @code{t}. @xref{Interactive Call}. |
| 1242 | |
| 1243 | The argument @var{default} specifies what to return if the user enters |
| 1244 | null input. It can be a symbol, a string or a list of strings. If it |
| 1245 | is a string, @code{read-command} interns it before returning it. |
| 1246 | If it is a list, @code{read-command} returns the first element of this list. |
| 1247 | If @var{default} is @code{nil}, that means no default has been |
| 1248 | specified; then if the user enters null input, the return value is |
| 1249 | @code{(intern "")}, that is, a symbol whose name is an empty string. |
| 1250 | |
| 1251 | @example |
| 1252 | (read-command "Command name? ") |
| 1253 | |
| 1254 | @group |
| 1255 | ;; @r{After evaluation of the preceding expression,} |
| 1256 | ;; @r{the following prompt appears with an empty minibuffer:} |
| 1257 | @end group |
| 1258 | |
| 1259 | @group |
| 1260 | ---------- Buffer: Minibuffer ---------- |
| 1261 | Command name? |
| 1262 | ---------- Buffer: Minibuffer ---------- |
| 1263 | @end group |
| 1264 | @end example |
| 1265 | |
| 1266 | @noindent |
| 1267 | If the user types @kbd{forward-c @key{RET}}, then this function returns |
| 1268 | @code{forward-char}. |
| 1269 | |
| 1270 | The @code{read-command} function is a simplified interface to |
| 1271 | @code{completing-read}. It uses the variable @code{obarray} so as to |
| 1272 | complete in the set of extant Lisp symbols, and it uses the |
| 1273 | @code{commandp} predicate so as to accept only command names: |
| 1274 | |
| 1275 | @cindex @code{commandp} example |
| 1276 | @example |
| 1277 | @group |
| 1278 | (read-command @var{prompt}) |
| 1279 | @equiv{} |
| 1280 | (intern (completing-read @var{prompt} obarray |
| 1281 | 'commandp t nil)) |
| 1282 | @end group |
| 1283 | @end example |
| 1284 | @end defun |
| 1285 | |
| 1286 | @defun read-variable prompt &optional default |
| 1287 | @anchor{Definition of read-variable} |
| 1288 | This function reads the name of a user variable and returns it as a |
| 1289 | symbol. |
| 1290 | |
| 1291 | The argument @var{default} specifies the default value to return if |
| 1292 | the user enters null input. It can be a symbol, a string, or a list |
| 1293 | of strings. If it is a string, @code{read-variable} interns it to |
| 1294 | make the default value. If it is a list, @code{read-variable} interns |
| 1295 | the first element. If @var{default} is @code{nil}, that means no |
| 1296 | default has been specified; then if the user enters null input, the |
| 1297 | return value is @code{(intern "")}. |
| 1298 | |
| 1299 | @example |
| 1300 | @group |
| 1301 | (read-variable "Variable name? ") |
| 1302 | |
| 1303 | ;; @r{After evaluation of the preceding expression,} |
| 1304 | ;; @r{the following prompt appears,} |
| 1305 | ;; @r{with an empty minibuffer:} |
| 1306 | @end group |
| 1307 | |
| 1308 | @group |
| 1309 | ---------- Buffer: Minibuffer ---------- |
| 1310 | Variable name? @point{} |
| 1311 | ---------- Buffer: Minibuffer ---------- |
| 1312 | @end group |
| 1313 | @end example |
| 1314 | |
| 1315 | @noindent |
| 1316 | If the user then types @kbd{fill-p @key{RET}}, @code{read-variable} |
| 1317 | returns @code{fill-prefix}. |
| 1318 | |
| 1319 | In general, @code{read-variable} is similar to @code{read-command}, |
| 1320 | but uses the predicate @code{user-variable-p} instead of |
| 1321 | @code{commandp}: |
| 1322 | |
| 1323 | @cindex @code{user-variable-p} example |
| 1324 | @example |
| 1325 | @group |
| 1326 | (read-variable @var{prompt}) |
| 1327 | @equiv{} |
| 1328 | (intern |
| 1329 | (completing-read @var{prompt} obarray |
| 1330 | 'user-variable-p t nil)) |
| 1331 | @end group |
| 1332 | @end example |
| 1333 | @end defun |
| 1334 | |
| 1335 | @deffn Command read-color &optional prompt convert allow-empty display |
| 1336 | This function reads a string that is a color specification, either the |
| 1337 | color's name or an RGB hex value such as @code{#RRRGGGBBB}. It |
| 1338 | prompts with @var{prompt} (default: @code{"Color (name or #R+G+B+):"}) |
| 1339 | and provides completion for color names, but not for hex RGB values. |
| 1340 | In addition to names of standard colors, completion candidates include |
| 1341 | the foreground and background colors at point. |
| 1342 | |
| 1343 | Valid RGB values are described in @ref{Color Names}. |
| 1344 | |
| 1345 | The function's return value is the color name typed by the user in the |
| 1346 | minibuffer. However, when called interactively or if the optional |
| 1347 | argument @var{convert} is non-@code{nil}, it converts the name into |
| 1348 | the color's RGB value and returns that value as a string. If an |
| 1349 | invalid color name was specified, this function signals an error, |
| 1350 | except that empty color names are allowed when @code{allow-empty} is |
| 1351 | non-@code{nil} and the user enters null input. |
| 1352 | |
| 1353 | Interactively, or when @var{display} is non-@code{nil}, the return |
| 1354 | value is also displayed in the echo area. |
| 1355 | @end deffn |
| 1356 | |
| 1357 | See also the functions @code{read-coding-system} and |
| 1358 | @code{read-non-nil-coding-system}, in @ref{User-Chosen Coding Systems}, |
| 1359 | and @code{read-input-method-name}, in @ref{Input Methods}. |
| 1360 | |
| 1361 | @node Reading File Names |
| 1362 | @subsection Reading File Names |
| 1363 | @cindex read file names |
| 1364 | @cindex prompt for file name |
| 1365 | |
| 1366 | The high-level completion functions @code{read-file-name}, |
| 1367 | @code{read-directory-name}, and @code{read-shell-command} are designed |
| 1368 | to read file names, directory names, and shell commands respectively. |
| 1369 | They provide special features, including automatic insertion of the |
| 1370 | default directory. |
| 1371 | |
| 1372 | @defun read-file-name prompt &optional directory default require-match initial predicate |
| 1373 | This function reads a file name, prompting with @var{prompt} and |
| 1374 | providing completion. |
| 1375 | |
| 1376 | As an exception, this function reads a file name using a graphical |
| 1377 | file dialog instead of the minibuffer, if (i) it is invoked via a |
| 1378 | mouse command, and (ii) the selected frame is on a graphical display |
| 1379 | supporting such dialogs, and (iii) the variable @code{use-dialog-box} |
| 1380 | is non-@code{nil} (@pxref{Dialog Boxes,, Dialog Boxes, emacs, The GNU |
| 1381 | Emacs Manual}), and (iv) the @var{directory} argument, described |
| 1382 | below, does not specify a remote file (@pxref{Remote Files,, Remote |
| 1383 | Files, emacs, The GNU Emacs Manual}). The exact behavior when using a |
| 1384 | graphical file dialog is platform-dependent. Here, we simply document |
| 1385 | the behavior when using the minibuffer. |
| 1386 | |
| 1387 | The optional argument @var{require-match} has the same meaning as in |
| 1388 | @code{completing-read}. @xref{Minibuffer Completion}. |
| 1389 | |
| 1390 | @code{read-file-name} uses |
| 1391 | @code{minibuffer-local-filename-completion-map} as the keymap if |
| 1392 | @var{require-match} is @code{nil}, and uses |
| 1393 | @code{minibuffer-local-filename-must-match-map} if @var{require-match} |
| 1394 | is non-@code{nil}. @xref{Completion Commands}. |
| 1395 | |
| 1396 | The argument @var{directory} specifies the directory to use for |
| 1397 | completion of relative file names. It should be an absolute directory |
| 1398 | name. If @code{insert-default-directory} is non-@code{nil}, |
| 1399 | @var{directory} is also inserted in the minibuffer as initial input. |
| 1400 | It defaults to the current buffer's value of @code{default-directory}. |
| 1401 | |
| 1402 | If you specify @var{initial}, that is an initial file name to insert |
| 1403 | in the buffer (after @var{directory}, if that is inserted). In this |
| 1404 | case, point goes at the beginning of @var{initial}. The default for |
| 1405 | @var{initial} is @code{nil}---don't insert any file name. To see what |
| 1406 | @var{initial} does, try the command @kbd{C-x C-v}. @strong{Please |
| 1407 | note:} we recommend using @var{default} rather than @var{initial} in |
| 1408 | most cases. |
| 1409 | |
| 1410 | If @var{default} is non-@code{nil}, then the function returns |
| 1411 | @var{default} if the user exits the minibuffer with the same non-empty |
| 1412 | contents that @code{read-file-name} inserted initially. The initial |
| 1413 | minibuffer contents are always non-empty if |
| 1414 | @code{insert-default-directory} is non-@code{nil}, as it is by |
| 1415 | default. @var{default} is not checked for validity, regardless of the |
| 1416 | value of @var{require-match}. However, if @var{require-match} is |
| 1417 | non-@code{nil}, the initial minibuffer contents should be a valid file |
| 1418 | (or directory) name. Otherwise @code{read-file-name} attempts |
| 1419 | completion if the user exits without any editing, and does not return |
| 1420 | @var{default}. @var{default} is also available through the history |
| 1421 | commands. |
| 1422 | |
| 1423 | If @var{default} is @code{nil}, @code{read-file-name} tries to find a |
| 1424 | substitute default to use in its place, which it treats in exactly the |
| 1425 | same way as if it had been specified explicitly. If @var{default} is |
| 1426 | @code{nil}, but @var{initial} is non-@code{nil}, then the default is |
| 1427 | the absolute file name obtained from @var{directory} and |
| 1428 | @var{initial}. If both @var{default} and @var{initial} are @code{nil} |
| 1429 | and the buffer is visiting a file, @code{read-file-name} uses the |
| 1430 | absolute file name of that file as default. If the buffer is not |
| 1431 | visiting a file, then there is no default. In that case, if the user |
| 1432 | types @key{RET} without any editing, @code{read-file-name} simply |
| 1433 | returns the pre-inserted contents of the minibuffer. |
| 1434 | |
| 1435 | If the user types @key{RET} in an empty minibuffer, this function |
| 1436 | returns an empty string, regardless of the value of |
| 1437 | @var{require-match}. This is, for instance, how the user can make the |
| 1438 | current buffer visit no file using @code{M-x set-visited-file-name}. |
| 1439 | |
| 1440 | If @var{predicate} is non-@code{nil}, it specifies a function of one |
| 1441 | argument that decides which file names are acceptable completion |
| 1442 | possibilities. A file name is an acceptable value if @var{predicate} |
| 1443 | returns non-@code{nil} for it. |
| 1444 | |
| 1445 | @code{read-file-name} does not automatically expand file names. You |
| 1446 | must call @code{expand-file-name} yourself if an absolute file name is |
| 1447 | required. |
| 1448 | |
| 1449 | Here is an example: |
| 1450 | |
| 1451 | @example |
| 1452 | @group |
| 1453 | (read-file-name "The file is ") |
| 1454 | |
| 1455 | ;; @r{After evaluation of the preceding expression,} |
| 1456 | ;; @r{the following appears in the minibuffer:} |
| 1457 | @end group |
| 1458 | |
| 1459 | @group |
| 1460 | ---------- Buffer: Minibuffer ---------- |
| 1461 | The file is /gp/gnu/elisp/@point{} |
| 1462 | ---------- Buffer: Minibuffer ---------- |
| 1463 | @end group |
| 1464 | @end example |
| 1465 | |
| 1466 | @noindent |
| 1467 | Typing @kbd{manual @key{TAB}} results in the following: |
| 1468 | |
| 1469 | @example |
| 1470 | @group |
| 1471 | ---------- Buffer: Minibuffer ---------- |
| 1472 | The file is /gp/gnu/elisp/manual.texi@point{} |
| 1473 | ---------- Buffer: Minibuffer ---------- |
| 1474 | @end group |
| 1475 | @end example |
| 1476 | |
| 1477 | @c Wordy to avoid overfull hbox in smallbook mode. |
| 1478 | @noindent |
| 1479 | If the user types @key{RET}, @code{read-file-name} returns the file name |
| 1480 | as the string @code{"/gp/gnu/elisp/manual.texi"}. |
| 1481 | @end defun |
| 1482 | |
| 1483 | @defvar read-file-name-function |
| 1484 | If non-@code{nil}, this should be a function that accepts the same |
| 1485 | arguments as @code{read-file-name}. When @code{read-file-name} is |
| 1486 | called, it calls this function with the supplied arguments instead of |
| 1487 | doing its usual work. |
| 1488 | @end defvar |
| 1489 | |
| 1490 | @defopt read-file-name-completion-ignore-case |
| 1491 | If this variable is non-@code{nil}, @code{read-file-name} ignores case |
| 1492 | when performing completion. |
| 1493 | @end defopt |
| 1494 | |
| 1495 | @defun read-directory-name prompt &optional directory default require-match initial |
| 1496 | This function is like @code{read-file-name} but allows only directory |
| 1497 | names as completion possibilities. |
| 1498 | |
| 1499 | If @var{default} is @code{nil} and @var{initial} is non-@code{nil}, |
| 1500 | @code{read-directory-name} constructs a substitute default by |
| 1501 | combining @var{directory} (or the current buffer's default directory |
| 1502 | if @var{directory} is @code{nil}) and @var{initial}. If both |
| 1503 | @var{default} and @var{initial} are @code{nil}, this function uses |
| 1504 | @var{directory} as substitute default, or the current buffer's default |
| 1505 | directory if @var{directory} is @code{nil}. |
| 1506 | @end defun |
| 1507 | |
| 1508 | @defopt insert-default-directory |
| 1509 | This variable is used by @code{read-file-name}, and thus, indirectly, |
| 1510 | by most commands reading file names. (This includes all commands that |
| 1511 | use the code letters @samp{f} or @samp{F} in their interactive form. |
| 1512 | @xref{Interactive Codes,, Code Characters for interactive}.) Its |
| 1513 | value controls whether @code{read-file-name} starts by placing the |
| 1514 | name of the default directory in the minibuffer, plus the initial file |
| 1515 | name if any. If the value of this variable is @code{nil}, then |
| 1516 | @code{read-file-name} does not place any initial input in the |
| 1517 | minibuffer (unless you specify initial input with the @var{initial} |
| 1518 | argument). In that case, the default directory is still used for |
| 1519 | completion of relative file names, but is not displayed. |
| 1520 | |
| 1521 | If this variable is @code{nil} and the initial minibuffer contents are |
| 1522 | empty, the user may have to explicitly fetch the next history element |
| 1523 | to access a default value. If the variable is non-@code{nil}, the |
| 1524 | initial minibuffer contents are always non-empty and the user can |
| 1525 | always request a default value by immediately typing @key{RET} in an |
| 1526 | unedited minibuffer. (See above.) |
| 1527 | |
| 1528 | For example: |
| 1529 | |
| 1530 | @example |
| 1531 | @group |
| 1532 | ;; @r{Here the minibuffer starts out with the default directory.} |
| 1533 | (let ((insert-default-directory t)) |
| 1534 | (read-file-name "The file is ")) |
| 1535 | @end group |
| 1536 | |
| 1537 | @group |
| 1538 | ---------- Buffer: Minibuffer ---------- |
| 1539 | The file is ~lewis/manual/@point{} |
| 1540 | ---------- Buffer: Minibuffer ---------- |
| 1541 | @end group |
| 1542 | |
| 1543 | @group |
| 1544 | ;; @r{Here the minibuffer is empty and only the prompt} |
| 1545 | ;; @r{appears on its line.} |
| 1546 | (let ((insert-default-directory nil)) |
| 1547 | (read-file-name "The file is ")) |
| 1548 | @end group |
| 1549 | |
| 1550 | @group |
| 1551 | ---------- Buffer: Minibuffer ---------- |
| 1552 | The file is @point{} |
| 1553 | ---------- Buffer: Minibuffer ---------- |
| 1554 | @end group |
| 1555 | @end example |
| 1556 | @end defopt |
| 1557 | |
| 1558 | @defun read-shell-command prompt &optional initial-contents hist &rest args |
| 1559 | This function reads a shell command from the minibuffer, prompting |
| 1560 | with @var{prompt} and providing intelligent completion. It completes |
| 1561 | the first word of the command using candidates that are appropriate |
| 1562 | for command names, and the rest of the command words as file names. |
| 1563 | |
| 1564 | This function uses @code{minibuffer-local-shell-command-map} as the |
| 1565 | keymap for minibuffer input. The @var{hist} argument specifies the |
| 1566 | history list to use; if is omitted or @code{nil}, it defaults to |
| 1567 | @code{shell-command-history} (@pxref{Minibuffer History, |
| 1568 | shell-command-history}). The optional argument @var{initial-contents} |
| 1569 | specifies the initial content of the minibuffer (@pxref{Initial |
| 1570 | Input}). The rest of @var{args}, if present, are used as the |
| 1571 | @var{default} and @var{inherit-input-method} arguments in |
| 1572 | @code{read-from-minibuffer} (@pxref{Text from Minibuffer}). |
| 1573 | @end defun |
| 1574 | |
| 1575 | @defvar minibuffer-local-shell-command-map |
| 1576 | This keymap is used by @code{read-shell-command} for completing |
| 1577 | command and file names that are part of a shell command. |
| 1578 | @end defvar |
| 1579 | |
| 1580 | @node Completion Styles |
| 1581 | @subsection Completion Styles |
| 1582 | @cindex completion styles |
| 1583 | |
| 1584 | A @dfn{completion style} is a set of rules for generating |
| 1585 | completions. The user option @code{completion-styles} stores a list |
| 1586 | of completion styles, which are represented by symbols. |
| 1587 | |
| 1588 | @defopt completion-styles |
| 1589 | This is a list of completion style symbols to use for performing |
| 1590 | completion. Each completion style in this list must be defined in |
| 1591 | @code{completion-styles-alist}. |
| 1592 | @end defopt |
| 1593 | |
| 1594 | @defvar completion-styles-alist |
| 1595 | This variable stores a list of available completion styles. Each |
| 1596 | element in the list must have the form @samp{(@var{name} |
| 1597 | @var{try-completion} @var{all-completions})}. Here, @var{name} is the |
| 1598 | name of the completion style (a symbol), which may be used in |
| 1599 | @code{completion-styles-alist} to refer to this style. |
| 1600 | |
| 1601 | @var{try-completion} is the function that does the completion, and |
| 1602 | @var{all-completions} is the function that lists the completions. |
| 1603 | These functions should accept four arguments: @var{string}, |
| 1604 | @var{collection}, @var{predicate}, and @var{point}. The @var{string}, |
| 1605 | @var{collection}, and @var{predicate} arguments have the same meanings |
| 1606 | as in @code{try-completion} (@pxref{Basic Completion}), and the |
| 1607 | @var{point} argument is the position of point within @var{string}. |
| 1608 | Each function should return a non-@code{nil} value if it performed its |
| 1609 | job, and @code{nil} if it did not (e.g., if there is no way to |
| 1610 | complete @var{string} according to the completion style). |
| 1611 | |
| 1612 | When the user calls a completion command, such as |
| 1613 | @code{minibuffer-complete} (@pxref{Completion Commands}), Emacs looks |
| 1614 | for the first style listed in @code{completion-styles} and calls its |
| 1615 | @var{try-completion} function. If this function returns @code{nil}, |
| 1616 | Emacs moves to the next completion style listed in |
| 1617 | @code{completion-styles} and calls its @var{try-completion} function, |
| 1618 | and so on until one of the @var{try-completion} functions successfully |
| 1619 | performs completion and returns a non-@code{nil} value. A similar |
| 1620 | procedure is used for listing completions, via the |
| 1621 | @var{all-completions} functions. |
| 1622 | @end defvar |
| 1623 | |
| 1624 | By default, @code{completion-styles-alist} contains five pre-defined |
| 1625 | completion styles: @code{basic}, a basic completion style; |
| 1626 | @code{partial-completion}, which does partial completion (completing |
| 1627 | each word in the input separately); @code{emacs22}, which performs |
| 1628 | completion according to the rules used in Emacs 22; @code{emacs21}, |
| 1629 | which performs completion according to the rules used in Emacs 21; and |
| 1630 | @code{initials}, which completes acronyms and initialisms. |
| 1631 | |
| 1632 | @node Programmed Completion |
| 1633 | @subsection Programmed Completion |
| 1634 | @cindex programmed completion |
| 1635 | |
| 1636 | Sometimes it is not possible to create an alist or an obarray |
| 1637 | containing all the intended possible completions. In such a case, you |
| 1638 | can supply your own function to compute the completion of a given |
| 1639 | string. This is called @dfn{programmed completion}. Emacs uses |
| 1640 | programmed completion when completing file names (@pxref{File Name |
| 1641 | Completion}), among many other cases. |
| 1642 | |
| 1643 | To use this feature, pass a function as the @var{collection} |
| 1644 | argument to @code{completing-read}. The function |
| 1645 | @code{completing-read} arranges to pass your completion function along |
| 1646 | to @code{try-completion}, @code{all-completions}, and other basic |
| 1647 | completion functions, which will then let your function do all |
| 1648 | the work. |
| 1649 | |
| 1650 | The completion function should accept three arguments: |
| 1651 | |
| 1652 | @itemize @bullet |
| 1653 | @item |
| 1654 | The string to be completed. |
| 1655 | |
| 1656 | @item |
| 1657 | The predicate function to filter possible matches, or @code{nil} if |
| 1658 | none. Your function should call the predicate for each possible match, |
| 1659 | and ignore the possible match if the predicate returns @code{nil}. |
| 1660 | |
| 1661 | @item |
| 1662 | A flag specifying the type of operation. The best way to think about |
| 1663 | it is that the function stands for an object (in the |
| 1664 | ``object-oriented'' sense of the word), and this third argument |
| 1665 | specifies which method to run. |
| 1666 | @end itemize |
| 1667 | |
| 1668 | There are currently four methods, i.e. four flag values, one for |
| 1669 | each of the four different basic operations: |
| 1670 | |
| 1671 | @itemize @bullet |
| 1672 | @item |
| 1673 | @code{nil} specifies @code{try-completion}. The completion function |
| 1674 | should return the completion of the specified string, or @code{t} if the |
| 1675 | string is a unique and exact match already, or @code{nil} if the string |
| 1676 | matches no possibility. |
| 1677 | |
| 1678 | If the string is an exact match for one possibility, but also matches |
| 1679 | other longer possibilities, the function should return the string, not |
| 1680 | @code{t}. |
| 1681 | |
| 1682 | @item |
| 1683 | @code{t} specifies @code{all-completions}. The completion function |
| 1684 | should return a list of all possible completions of the specified |
| 1685 | string. |
| 1686 | |
| 1687 | @item |
| 1688 | @code{lambda} specifies @code{test-completion}. The completion |
| 1689 | function should return @code{t} if the specified string is an exact |
| 1690 | match for some possibility; @code{nil} otherwise. |
| 1691 | |
| 1692 | @item |
| 1693 | @code{(boundaries . SUFFIX)} specifies @code{completion-boundaries}. |
| 1694 | The function should return a value of the form @code{(boundaries |
| 1695 | START . END)} where START is the position of the beginning boundary in |
| 1696 | in the string to complete, and END is the position of the end boundary |
| 1697 | in SUFFIX. |
| 1698 | @end itemize |
| 1699 | |
| 1700 | It would be consistent and clean for completion functions to allow |
| 1701 | lambda expressions (lists that are functions) as well as function |
| 1702 | symbols as @var{collection}, but this is impossible. Lists as |
| 1703 | completion tables already have other meanings, and it would be |
| 1704 | unreliable to treat one differently just because it is also a possible |
| 1705 | function. So you must arrange for any function you wish to use for |
| 1706 | completion to be encapsulated in a symbol. |
| 1707 | |
| 1708 | @defun completion-table-dynamic function |
| 1709 | This function is a convenient way to write a function that can act as |
| 1710 | programmed completion function. The argument @var{function} should be |
| 1711 | a function that takes one argument, a string, and returns an alist of |
| 1712 | possible completions of it. You can think of |
| 1713 | @code{completion-table-dynamic} as a transducer between that interface |
| 1714 | and the interface for programmed completion functions. |
| 1715 | @end defun |
| 1716 | |
| 1717 | @defvar completion-annotate-function |
| 1718 | The value of this variable, if non-@code{nil}, should be a function |
| 1719 | for ``annotating'' the entries in the @samp{*Completions*} buffer. |
| 1720 | The function should accept a single argument, the completion string |
| 1721 | for an entry. It should return an additional string to display next |
| 1722 | to that entry in the @samp{*Completions*} buffer, or @code{nil} if no |
| 1723 | additional string is to be displayed. |
| 1724 | |
| 1725 | The function can determine the collection used for the current |
| 1726 | completion via the variable @code{minibuffer-completion-table} |
| 1727 | (@pxref{Completion Commands}). |
| 1728 | @end defvar |
| 1729 | |
| 1730 | @node Yes-or-No Queries |
| 1731 | @section Yes-or-No Queries |
| 1732 | @cindex asking the user questions |
| 1733 | @cindex querying the user |
| 1734 | @cindex yes-or-no questions |
| 1735 | |
| 1736 | This section describes functions used to ask the user a yes-or-no |
| 1737 | question. The function @code{y-or-n-p} can be answered with a single |
| 1738 | character; it is useful for questions where an inadvertent wrong answer |
| 1739 | will not have serious consequences. @code{yes-or-no-p} is suitable for |
| 1740 | more momentous questions, since it requires three or four characters to |
| 1741 | answer. |
| 1742 | |
| 1743 | If either of these functions is called in a command that was invoked |
| 1744 | using the mouse---more precisely, if @code{last-nonmenu-event} |
| 1745 | (@pxref{Command Loop Info}) is either @code{nil} or a list---then it |
| 1746 | uses a dialog box or pop-up menu to ask the question. Otherwise, it |
| 1747 | uses keyboard input. You can force use of the mouse or use of keyboard |
| 1748 | input by binding @code{last-nonmenu-event} to a suitable value around |
| 1749 | the call. |
| 1750 | |
| 1751 | Strictly speaking, @code{yes-or-no-p} uses the minibuffer and |
| 1752 | @code{y-or-n-p} does not; but it seems best to describe them together. |
| 1753 | |
| 1754 | @defun y-or-n-p prompt |
| 1755 | This function asks the user a question, expecting input in the echo |
| 1756 | area. It returns @code{t} if the user types @kbd{y}, @code{nil} if the |
| 1757 | user types @kbd{n}. This function also accepts @key{SPC} to mean yes |
| 1758 | and @key{DEL} to mean no. It accepts @kbd{C-]} to mean ``quit,'' like |
| 1759 | @kbd{C-g}, because the question might look like a minibuffer and for |
| 1760 | that reason the user might try to use @kbd{C-]} to get out. The answer |
| 1761 | is a single character, with no @key{RET} needed to terminate it. Upper |
| 1762 | and lower case are equivalent. |
| 1763 | |
| 1764 | ``Asking the question'' means printing @var{prompt} in the echo area, |
| 1765 | followed by the string @w{@samp{(y or n) }}. If the input is not one of |
| 1766 | the expected answers (@kbd{y}, @kbd{n}, @kbd{@key{SPC}}, |
| 1767 | @kbd{@key{DEL}}, or something that quits), the function responds |
| 1768 | @samp{Please answer y or n.}, and repeats the request. |
| 1769 | |
| 1770 | This function does not actually use the minibuffer, since it does not |
| 1771 | allow editing of the answer. It actually uses the echo area (@pxref{The |
| 1772 | Echo Area}), which uses the same screen space as the minibuffer. The |
| 1773 | cursor moves to the echo area while the question is being asked. |
| 1774 | |
| 1775 | The answers and their meanings, even @samp{y} and @samp{n}, are not |
| 1776 | hardwired. The keymap @code{query-replace-map} specifies them. |
| 1777 | @xref{Search and Replace}. |
| 1778 | |
| 1779 | In the following example, the user first types @kbd{q}, which is |
| 1780 | invalid. At the next prompt the user types @kbd{y}. |
| 1781 | |
| 1782 | @smallexample |
| 1783 | @group |
| 1784 | (y-or-n-p "Do you need a lift? ") |
| 1785 | |
| 1786 | ;; @r{After evaluation of the preceding expression,} |
| 1787 | ;; @r{the following prompt appears in the echo area:} |
| 1788 | @end group |
| 1789 | |
| 1790 | @group |
| 1791 | ---------- Echo area ---------- |
| 1792 | Do you need a lift? (y or n) |
| 1793 | ---------- Echo area ---------- |
| 1794 | @end group |
| 1795 | |
| 1796 | ;; @r{If the user then types @kbd{q}, the following appears:} |
| 1797 | |
| 1798 | @group |
| 1799 | ---------- Echo area ---------- |
| 1800 | Please answer y or n. Do you need a lift? (y or n) |
| 1801 | ---------- Echo area ---------- |
| 1802 | @end group |
| 1803 | |
| 1804 | ;; @r{When the user types a valid answer,} |
| 1805 | ;; @r{it is displayed after the question:} |
| 1806 | |
| 1807 | @group |
| 1808 | ---------- Echo area ---------- |
| 1809 | Do you need a lift? (y or n) y |
| 1810 | ---------- Echo area ---------- |
| 1811 | @end group |
| 1812 | @end smallexample |
| 1813 | |
| 1814 | @noindent |
| 1815 | We show successive lines of echo area messages, but only one actually |
| 1816 | appears on the screen at a time. |
| 1817 | @end defun |
| 1818 | |
| 1819 | @defun y-or-n-p-with-timeout prompt seconds default-value |
| 1820 | Like @code{y-or-n-p}, except that if the user fails to answer within |
| 1821 | @var{seconds} seconds, this function stops waiting and returns |
| 1822 | @var{default-value}. It works by setting up a timer; see @ref{Timers}. |
| 1823 | The argument @var{seconds} may be an integer or a floating point number. |
| 1824 | @end defun |
| 1825 | |
| 1826 | @defun yes-or-no-p prompt |
| 1827 | This function asks the user a question, expecting input in the |
| 1828 | minibuffer. It returns @code{t} if the user enters @samp{yes}, |
| 1829 | @code{nil} if the user types @samp{no}. The user must type @key{RET} to |
| 1830 | finalize the response. Upper and lower case are equivalent. |
| 1831 | |
| 1832 | @code{yes-or-no-p} starts by displaying @var{prompt} in the echo area, |
| 1833 | followed by @w{@samp{(yes or no) }}. The user must type one of the |
| 1834 | expected responses; otherwise, the function responds @samp{Please answer |
| 1835 | yes or no.}, waits about two seconds and repeats the request. |
| 1836 | |
| 1837 | @code{yes-or-no-p} requires more work from the user than |
| 1838 | @code{y-or-n-p} and is appropriate for more crucial decisions. |
| 1839 | |
| 1840 | Here is an example: |
| 1841 | |
| 1842 | @smallexample |
| 1843 | @group |
| 1844 | (yes-or-no-p "Do you really want to remove everything? ") |
| 1845 | |
| 1846 | ;; @r{After evaluation of the preceding expression,} |
| 1847 | ;; @r{the following prompt appears,} |
| 1848 | ;; @r{with an empty minibuffer:} |
| 1849 | @end group |
| 1850 | |
| 1851 | @group |
| 1852 | ---------- Buffer: minibuffer ---------- |
| 1853 | Do you really want to remove everything? (yes or no) |
| 1854 | ---------- Buffer: minibuffer ---------- |
| 1855 | @end group |
| 1856 | @end smallexample |
| 1857 | |
| 1858 | @noindent |
| 1859 | If the user first types @kbd{y @key{RET}}, which is invalid because this |
| 1860 | function demands the entire word @samp{yes}, it responds by displaying |
| 1861 | these prompts, with a brief pause between them: |
| 1862 | |
| 1863 | @smallexample |
| 1864 | @group |
| 1865 | ---------- Buffer: minibuffer ---------- |
| 1866 | Please answer yes or no. |
| 1867 | Do you really want to remove everything? (yes or no) |
| 1868 | ---------- Buffer: minibuffer ---------- |
| 1869 | @end group |
| 1870 | @end smallexample |
| 1871 | @end defun |
| 1872 | |
| 1873 | @node Multiple Queries |
| 1874 | @section Asking Multiple Y-or-N Questions |
| 1875 | |
| 1876 | When you have a series of similar questions to ask, such as ``Do you |
| 1877 | want to save this buffer'' for each buffer in turn, you should use |
| 1878 | @code{map-y-or-n-p} to ask the collection of questions, rather than |
| 1879 | asking each question individually. This gives the user certain |
| 1880 | convenient facilities such as the ability to answer the whole series at |
| 1881 | once. |
| 1882 | |
| 1883 | @defun map-y-or-n-p prompter actor list &optional help action-alist no-cursor-in-echo-area |
| 1884 | This function asks the user a series of questions, reading a |
| 1885 | single-character answer in the echo area for each one. |
| 1886 | |
| 1887 | The value of @var{list} specifies the objects to ask questions about. |
| 1888 | It should be either a list of objects or a generator function. If it is |
| 1889 | a function, it should expect no arguments, and should return either the |
| 1890 | next object to ask about, or @code{nil} meaning stop asking questions. |
| 1891 | |
| 1892 | The argument @var{prompter} specifies how to ask each question. If |
| 1893 | @var{prompter} is a string, the question text is computed like this: |
| 1894 | |
| 1895 | @example |
| 1896 | (format @var{prompter} @var{object}) |
| 1897 | @end example |
| 1898 | |
| 1899 | @noindent |
| 1900 | where @var{object} is the next object to ask about (as obtained from |
| 1901 | @var{list}). |
| 1902 | |
| 1903 | If not a string, @var{prompter} should be a function of one argument |
| 1904 | (the next object to ask about) and should return the question text. If |
| 1905 | the value is a string, that is the question to ask the user. The |
| 1906 | function can also return @code{t} meaning do act on this object (and |
| 1907 | don't ask the user), or @code{nil} meaning ignore this object (and don't |
| 1908 | ask the user). |
| 1909 | |
| 1910 | The argument @var{actor} says how to act on the answers that the user |
| 1911 | gives. It should be a function of one argument, and it is called with |
| 1912 | each object that the user says yes for. Its argument is always an |
| 1913 | object obtained from @var{list}. |
| 1914 | |
| 1915 | If the argument @var{help} is given, it should be a list of this form: |
| 1916 | |
| 1917 | @example |
| 1918 | (@var{singular} @var{plural} @var{action}) |
| 1919 | @end example |
| 1920 | |
| 1921 | @noindent |
| 1922 | where @var{singular} is a string containing a singular noun that |
| 1923 | describes the objects conceptually being acted on, @var{plural} is the |
| 1924 | corresponding plural noun, and @var{action} is a transitive verb |
| 1925 | describing what @var{actor} does. |
| 1926 | |
| 1927 | If you don't specify @var{help}, the default is @code{("object" |
| 1928 | "objects" "act on")}. |
| 1929 | |
| 1930 | Each time a question is asked, the user may enter @kbd{y}, @kbd{Y}, or |
| 1931 | @key{SPC} to act on that object; @kbd{n}, @kbd{N}, or @key{DEL} to skip |
| 1932 | that object; @kbd{!} to act on all following objects; @key{ESC} or |
| 1933 | @kbd{q} to exit (skip all following objects); @kbd{.} (period) to act on |
| 1934 | the current object and then exit; or @kbd{C-h} to get help. These are |
| 1935 | the same answers that @code{query-replace} accepts. The keymap |
| 1936 | @code{query-replace-map} defines their meaning for @code{map-y-or-n-p} |
| 1937 | as well as for @code{query-replace}; see @ref{Search and Replace}. |
| 1938 | |
| 1939 | You can use @var{action-alist} to specify additional possible answers |
| 1940 | and what they mean. It is an alist of elements of the form |
| 1941 | @code{(@var{char} @var{function} @var{help})}, each of which defines one |
| 1942 | additional answer. In this element, @var{char} is a character (the |
| 1943 | answer); @var{function} is a function of one argument (an object from |
| 1944 | @var{list}); @var{help} is a string. |
| 1945 | |
| 1946 | When the user responds with @var{char}, @code{map-y-or-n-p} calls |
| 1947 | @var{function}. If it returns non-@code{nil}, the object is considered |
| 1948 | ``acted upon,'' and @code{map-y-or-n-p} advances to the next object in |
| 1949 | @var{list}. If it returns @code{nil}, the prompt is repeated for the |
| 1950 | same object. |
| 1951 | |
| 1952 | Normally, @code{map-y-or-n-p} binds @code{cursor-in-echo-area} while |
| 1953 | prompting. But if @var{no-cursor-in-echo-area} is non-@code{nil}, it |
| 1954 | does not do that. |
| 1955 | |
| 1956 | If @code{map-y-or-n-p} is called in a command that was invoked using the |
| 1957 | mouse---more precisely, if @code{last-nonmenu-event} (@pxref{Command |
| 1958 | Loop Info}) is either @code{nil} or a list---then it uses a dialog box |
| 1959 | or pop-up menu to ask the question. In this case, it does not use |
| 1960 | keyboard input or the echo area. You can force use of the mouse or use |
| 1961 | of keyboard input by binding @code{last-nonmenu-event} to a suitable |
| 1962 | value around the call. |
| 1963 | |
| 1964 | The return value of @code{map-y-or-n-p} is the number of objects acted on. |
| 1965 | @end defun |
| 1966 | |
| 1967 | @node Reading a Password |
| 1968 | @section Reading a Password |
| 1969 | @cindex passwords, reading |
| 1970 | |
| 1971 | To read a password to pass to another program, you can use the |
| 1972 | function @code{read-passwd}. |
| 1973 | |
| 1974 | @defun read-passwd prompt &optional confirm default |
| 1975 | This function reads a password, prompting with @var{prompt}. It does |
| 1976 | not echo the password as the user types it; instead, it echoes @samp{.} |
| 1977 | for each character in the password. |
| 1978 | |
| 1979 | The optional argument @var{confirm}, if non-@code{nil}, says to read the |
| 1980 | password twice and insist it must be the same both times. If it isn't |
| 1981 | the same, the user has to type it over and over until the last two |
| 1982 | times match. |
| 1983 | |
| 1984 | The optional argument @var{default} specifies the default password to |
| 1985 | return if the user enters empty input. If @var{default} is @code{nil}, |
| 1986 | then @code{read-passwd} returns the null string in that case. |
| 1987 | @end defun |
| 1988 | |
| 1989 | @node Minibuffer Commands |
| 1990 | @section Minibuffer Commands |
| 1991 | |
| 1992 | This section describes some commands meant for use in the |
| 1993 | minibuffer. |
| 1994 | |
| 1995 | @deffn Command exit-minibuffer |
| 1996 | This command exits the active minibuffer. It is normally bound to |
| 1997 | keys in minibuffer local keymaps. |
| 1998 | @end deffn |
| 1999 | |
| 2000 | @deffn Command self-insert-and-exit |
| 2001 | This command exits the active minibuffer after inserting the last |
| 2002 | character typed on the keyboard (found in @code{last-command-event}; |
| 2003 | @pxref{Command Loop Info}). |
| 2004 | @end deffn |
| 2005 | |
| 2006 | @deffn Command previous-history-element n |
| 2007 | This command replaces the minibuffer contents with the value of the |
| 2008 | @var{n}th previous (older) history element. |
| 2009 | @end deffn |
| 2010 | |
| 2011 | @deffn Command next-history-element n |
| 2012 | This command replaces the minibuffer contents with the value of the |
| 2013 | @var{n}th more recent history element. |
| 2014 | @end deffn |
| 2015 | |
| 2016 | @deffn Command previous-matching-history-element pattern n |
| 2017 | This command replaces the minibuffer contents with the value of the |
| 2018 | @var{n}th previous (older) history element that matches @var{pattern} (a |
| 2019 | regular expression). |
| 2020 | @end deffn |
| 2021 | |
| 2022 | @deffn Command next-matching-history-element pattern n |
| 2023 | This command replaces the minibuffer contents with the value of the |
| 2024 | @var{n}th next (newer) history element that matches @var{pattern} (a |
| 2025 | regular expression). |
| 2026 | @end deffn |
| 2027 | |
| 2028 | @node Minibuffer Windows |
| 2029 | @section Minibuffer Windows |
| 2030 | @cindex minibuffer windows |
| 2031 | |
| 2032 | These functions access and select minibuffer windows |
| 2033 | and test whether they are active. |
| 2034 | |
| 2035 | @defun active-minibuffer-window |
| 2036 | This function returns the currently active minibuffer window, or |
| 2037 | @code{nil} if none is currently active. |
| 2038 | @end defun |
| 2039 | |
| 2040 | @defun minibuffer-window &optional frame |
| 2041 | @anchor{Definition of minibuffer-window} |
| 2042 | This function returns the minibuffer window used for frame @var{frame}. |
| 2043 | If @var{frame} is @code{nil}, that stands for the current frame. Note |
| 2044 | that the minibuffer window used by a frame need not be part of that |
| 2045 | frame---a frame that has no minibuffer of its own necessarily uses some |
| 2046 | other frame's minibuffer window. |
| 2047 | @end defun |
| 2048 | |
| 2049 | @defun set-minibuffer-window window |
| 2050 | This function specifies @var{window} as the minibuffer window to use. |
| 2051 | This affects where the minibuffer is displayed if you put text in it |
| 2052 | without invoking the usual minibuffer commands. It has no effect on |
| 2053 | the usual minibuffer input functions because they all start by |
| 2054 | choosing the minibuffer window according to the current frame. |
| 2055 | @end defun |
| 2056 | |
| 2057 | @c Emacs 19 feature |
| 2058 | @defun window-minibuffer-p &optional window |
| 2059 | This function returns non-@code{nil} if @var{window} is a minibuffer |
| 2060 | window. |
| 2061 | @var{window} defaults to the selected window. |
| 2062 | @end defun |
| 2063 | |
| 2064 | It is not correct to determine whether a given window is a minibuffer by |
| 2065 | comparing it with the result of @code{(minibuffer-window)}, because |
| 2066 | there can be more than one minibuffer window if there is more than one |
| 2067 | frame. |
| 2068 | |
| 2069 | @defun minibuffer-window-active-p window |
| 2070 | This function returns non-@code{nil} if @var{window}, assumed to be |
| 2071 | a minibuffer window, is currently active. |
| 2072 | @end defun |
| 2073 | |
| 2074 | @node Minibuffer Contents |
| 2075 | @section Minibuffer Contents |
| 2076 | |
| 2077 | These functions access the minibuffer prompt and contents. |
| 2078 | |
| 2079 | @defun minibuffer-prompt |
| 2080 | This function returns the prompt string of the currently active |
| 2081 | minibuffer. If no minibuffer is active, it returns @code{nil}. |
| 2082 | @end defun |
| 2083 | |
| 2084 | @defun minibuffer-prompt-end |
| 2085 | This function returns the current |
| 2086 | position of the end of the minibuffer prompt, if a minibuffer is |
| 2087 | current. Otherwise, it returns the minimum valid buffer position. |
| 2088 | @end defun |
| 2089 | |
| 2090 | @defun minibuffer-prompt-width |
| 2091 | This function returns the current display-width of the minibuffer |
| 2092 | prompt, if a minibuffer is current. Otherwise, it returns zero. |
| 2093 | @end defun |
| 2094 | |
| 2095 | @defun minibuffer-contents |
| 2096 | This function returns the editable |
| 2097 | contents of the minibuffer (that is, everything except the prompt) as |
| 2098 | a string, if a minibuffer is current. Otherwise, it returns the |
| 2099 | entire contents of the current buffer. |
| 2100 | @end defun |
| 2101 | |
| 2102 | @defun minibuffer-contents-no-properties |
| 2103 | This is like @code{minibuffer-contents}, except that it does not copy text |
| 2104 | properties, just the characters themselves. @xref{Text Properties}. |
| 2105 | @end defun |
| 2106 | |
| 2107 | @defun minibuffer-completion-contents |
| 2108 | This is like @code{minibuffer-contents}, except that it returns only |
| 2109 | the contents before point. That is the part that completion commands |
| 2110 | operate on. @xref{Minibuffer Completion}. |
| 2111 | @end defun |
| 2112 | |
| 2113 | @defun delete-minibuffer-contents |
| 2114 | This function erases the editable contents of the minibuffer (that is, |
| 2115 | everything except the prompt), if a minibuffer is current. Otherwise, |
| 2116 | it erases the entire current buffer. |
| 2117 | @end defun |
| 2118 | |
| 2119 | @node Recursive Mini |
| 2120 | @section Recursive Minibuffers |
| 2121 | @cindex recursive minibuffers |
| 2122 | |
| 2123 | These functions and variables deal with recursive minibuffers |
| 2124 | (@pxref{Recursive Editing}): |
| 2125 | |
| 2126 | @defun minibuffer-depth |
| 2127 | This function returns the current depth of activations of the |
| 2128 | minibuffer, a nonnegative integer. If no minibuffers are active, it |
| 2129 | returns zero. |
| 2130 | @end defun |
| 2131 | |
| 2132 | @defopt enable-recursive-minibuffers |
| 2133 | If this variable is non-@code{nil}, you can invoke commands (such as |
| 2134 | @code{find-file}) that use minibuffers even while the minibuffer window |
| 2135 | is active. Such invocation produces a recursive editing level for a new |
| 2136 | minibuffer. The outer-level minibuffer is invisible while you are |
| 2137 | editing the inner one. |
| 2138 | |
| 2139 | If this variable is @code{nil}, you cannot invoke minibuffer |
| 2140 | commands when the minibuffer window is active, not even if you switch to |
| 2141 | another window to do it. |
| 2142 | @end defopt |
| 2143 | |
| 2144 | @c Emacs 19 feature |
| 2145 | If a command name has a property @code{enable-recursive-minibuffers} |
| 2146 | that is non-@code{nil}, then the command can use the minibuffer to read |
| 2147 | arguments even if it is invoked from the minibuffer. A command can |
| 2148 | also achieve this by binding @code{enable-recursive-minibuffers} |
| 2149 | to @code{t} in the interactive declaration (@pxref{Using Interactive}). |
| 2150 | The minibuffer command @code{next-matching-history-element} (normally |
| 2151 | @kbd{M-s} in the minibuffer) does the latter. |
| 2152 | |
| 2153 | @node Minibuffer Misc |
| 2154 | @section Minibuffer Miscellany |
| 2155 | |
| 2156 | @defun minibufferp &optional buffer-or-name |
| 2157 | This function returns non-@code{nil} if @var{buffer-or-name} is a |
| 2158 | minibuffer. If @var{buffer-or-name} is omitted, it tests the current |
| 2159 | buffer. |
| 2160 | @end defun |
| 2161 | |
| 2162 | @defvar minibuffer-setup-hook |
| 2163 | This is a normal hook that is run whenever the minibuffer is entered. |
| 2164 | @xref{Hooks}. |
| 2165 | @end defvar |
| 2166 | |
| 2167 | @defvar minibuffer-exit-hook |
| 2168 | This is a normal hook that is run whenever the minibuffer is exited. |
| 2169 | @xref{Hooks}. |
| 2170 | @end defvar |
| 2171 | |
| 2172 | @defvar minibuffer-help-form |
| 2173 | @anchor{Definition of minibuffer-help-form} |
| 2174 | The current value of this variable is used to rebind @code{help-form} |
| 2175 | locally inside the minibuffer (@pxref{Help Functions}). |
| 2176 | @end defvar |
| 2177 | |
| 2178 | @defvar minibuffer-scroll-window |
| 2179 | @anchor{Definition of minibuffer-scroll-window} |
| 2180 | If the value of this variable is non-@code{nil}, it should be a window |
| 2181 | object. When the function @code{scroll-other-window} is called in the |
| 2182 | minibuffer, it scrolls this window. |
| 2183 | @end defvar |
| 2184 | |
| 2185 | @defun minibuffer-selected-window |
| 2186 | This function returns the window which was selected when the |
| 2187 | minibuffer was entered. If selected window is not a minibuffer |
| 2188 | window, it returns @code{nil}. |
| 2189 | @end defun |
| 2190 | |
| 2191 | @defopt max-mini-window-height |
| 2192 | This variable specifies the maximum height for resizing minibuffer |
| 2193 | windows. If a float, it specifies a fraction of the height of the |
| 2194 | frame. If an integer, it specifies a number of lines. |
| 2195 | @end defopt |
| 2196 | |
| 2197 | @defun minibuffer-message string &rest args |
| 2198 | This function displays @var{string} temporarily at the end of the |
| 2199 | minibuffer text, for two seconds, or until the next input event |
| 2200 | arrives, whichever comes first. If @var{args} is non-@code{nil}, the |
| 2201 | actual message is obtained by passing @var{string} and @var{args} |
| 2202 | through @code{format}. @xref{Formatting Strings}. |
| 2203 | @end defun |