Mercurial > emacs
diff lispref/minibuf.texi @ 12098:a6eb5f12b0f3
*** empty log message ***
author | Karl Heuer <kwzh@gnu.org> |
---|---|
date | Tue, 06 Jun 1995 19:21:15 +0000 |
parents | 73dc8205d259 |
children | af994773013b |
line wrap: on
line diff
--- a/lispref/minibuf.texi Tue Jun 06 03:11:10 1995 +0000 +++ b/lispref/minibuf.texi Tue Jun 06 19:21:15 1995 +0000 @@ -61,7 +61,7 @@ Like other buffers, a minibuffer may use any of several local keymaps (@pxref{Keymaps}); these contain various exit commands and in some cases -completion commands. @xref{Completion}. +completion commands (@pxref{Completion}). @itemize @bullet @item @@ -87,6 +87,11 @@ primitive for minibuffer input is @code{read-from-minibuffer}; it can do either one. + In most cases, you should not call minibuffer input functions in the +middle of a Lisp function. Instead, do all minibuffer input as part of +reading the arguments for a command, in the @code{interactive} spec. +@xref{Defining Commands}. + @defun read-from-minibuffer prompt-string &optional initial-contents keymap read hist This function is the most general way to get input through the minibuffer. By default, it accepts arbitrary text and returns it as a @@ -199,12 +204,9 @@ @defvar minibuffer-local-ns-map This built-in variable is the keymap used as the minibuffer local keymap in the function @code{read-no-blanks-input}. By default, it makes the -following bindings: +following bindings, in addition to those of @code{minibuffer-local-map}: @table @asis -@item @key{LFD} -@code{exit-minibuffer} - @item @key{SPC} @cindex @key{SPC} in minibuffer @code{exit-minibuffer} @@ -213,27 +215,9 @@ @cindex @key{TAB} in minibuffer @code{exit-minibuffer} -@item @key{RET} -@code{exit-minibuffer} - -@item @kbd{C-g} -@code{abort-recursive-edit} - @item @kbd{?} @cindex @kbd{?} in minibuffer @code{self-insert-and-exit} - -@item @kbd{M-n} -@code{next-history-element} - -@item @kbd{M-p} -@code{previous-history-element} - -@item @kbd{M-r} -@code{next-matching-history-element} - -@item @kbd{M-s} -@code{previous-matching-history-element} @end table @end defvar @@ -805,6 +789,11 @@ This section describes the higher-level convenient functions for reading certain sorts of names with completion. + In most cases, you should not call these functions in the middle of a +Lisp function. When possible, do all minibuffer input as part of +reading the arguments for a command, in the @code{interactive} spec. +@xref{Defining Commands}. + @defun read-buffer prompt &optional default existing This function reads the name of a buffer and returns it as a string. The argument @var{default} is the default name to use, the value to @@ -1000,7 +989,8 @@ whether @code{read-file-name} starts by placing the name of the default directory in the minibuffer, plus the initial file name if any. If the value of this variable is @code{nil}, then @code{read-file-name} does -not place any initial input in the minibuffer. In that case, the +not place any initial input in the minibuffer (unless you specify +initial input with the @var{initial} argument). In that case, the default directory is still used for completion of relative file names, but is not displayed. @@ -1085,7 +1075,7 @@ @end itemize It would be consistent and clean for completion functions to allow -lambda expressions (lists tha are functions) as well as function +lambda expressions (lists that are functions) as well as function symbols as @var{collection}, but this is impossible. Lists as completion tables are already assigned another meaning---as alists. It would be unreliable to fail to handle an alist normally because it is @@ -1357,6 +1347,16 @@ expression). @end deffn +@defun minibuffer-prompt +This function returns the prompt string of the currently active +minibuffer. If no minibuffer is active, it returns @code{nil}. +@end defun + +@defun minibuffer-prompt-width +This function returns the display width of the prompt string of the +currently active minibuffer. If no minibuffer is active, it returns 0. +@end defun + @defvar minibuffer-setup-hook This is a normal hook that is run whenever the minibuffer is entered. @xref{Hooks}. @@ -1415,16 +1415,6 @@ returns zero. @end defun -@defun minibuffer-prompt -This function returns the prompt string of the currently active -minibuffer. If no minibuffer is active, it returns @code{nil}. -@end defun - -@defun minibuffer-prompt-width -This function returns the display width of the prompt string of the -currently active minibuffer. If no minibuffer is active, it returns 0. -@end defun - @defopt enable-recursive-minibuffers If this variable is non-@code{nil}, you can invoke commands (such as @code{find-file}) that use minibuffers even while in the minibuffer @@ -1442,5 +1432,5 @@ If a command name has a property @code{enable-recursive-minibuffers} that is non-@code{nil}, then the command can use the minibuffer to read arguments even if it is invoked from the minibuffer. The minibuffer -command @code{next-matching-history-element} (normally bound to -@kbd{M-s} in the minibuffer) uses this feature. +command @code{next-matching-history-element} (normally @kbd{M-s} in the +minibuffer) uses this feature.