X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/63d336640effbaa2ebc6d217bc70819d0897e595..db8d59365b5ccdca367ace2d4df5b8a2242e5765:/lispref/minibuf.texi

diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index 2fca6cc04b..d4f94e5269 100644
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -208,8 +208,10 @@ properties unconditionally, regardless of the value of this variable.
 @end defvar
 
 @defvar minibuffer-local-map
+This
 @anchor{Definition of minibuffer-local-map}
-This is the default local keymap for reading from the minibuffer.  By
+@c avoid page break at anchor; work around Texinfo deficiency
+is the default local keymap for reading from the minibuffer.  By
 default, it makes the following bindings:
 
 @table @asis
@@ -460,6 +462,14 @@ However, if @var{keep-all} is non-@code{nil}, that says not to remove
 duplicates, and to add @var{newelt} to the list even if it is empty.
 @end defun
 
+@defvar history-add-new-input
+If the value of this variable is @code{nil}, standard functions that
+read from the minibuffer don't add new elements to the history list.
+This lets Lisp programs explicitly manage input history by using
+@code{add-to-history}.  By default, @code{history-add-new-input} is
+set to a non-@code{nil} value.
+@end defvar
+
 @defvar history-length
 The value of this variable specifies the maximum length for all
 history lists that don't specify their own maximum lengths.  If the
@@ -1191,8 +1201,9 @@ Variable name? @point{}
 If the user then types @kbd{fill-p @key{RET}}, @code{read-variable}
 returns @code{fill-prefix}.
 
-This function is similar to @code{read-command}, but uses the
-predicate @code{user-variable-p} instead of @code{commandp}:
+In general, @code{read-variable} is similar to @code{read-command},
+but uses the predicate @code{user-variable-p} instead of
+@code{commandp}:
 
 @cindex @code{user-variable-p} example
 @example
@@ -1229,7 +1240,7 @@ value of @var{existing} is neither @code{nil} nor @code{t}, then
 @var{existing} is @code{nil}, then the name of a nonexistent file is
 acceptable.
 
-The function @code{read-file-name} uses
+@code{read-file-name} uses
 @code{minibuffer-local-filename-completion-map} as the keymap if
 @var{existing} is @code{nil}, and uses
 @code{minibuffer-local-must-match-filename-map} if @var{existing} is
@@ -1500,7 +1511,7 @@ the call.
 This function asks the user a question, expecting input in the echo
 area.  It returns @code{t} if the user types @kbd{y}, @code{nil} if the
 user types @kbd{n}.  This function also accepts @key{SPC} to mean yes
-and @key{DEL} to mean no.  It accepts @kbd{C-]} to mean ``quit'', like
+and @key{DEL} to mean no.  It accepts @kbd{C-]} to mean ``quit,'' like
 @kbd{C-g}, because the question might look like a minibuffer and for
 that reason the user might try to use @kbd{C-]} to get out.  The answer
 is a single character, with no @key{RET} needed to terminate it.  Upper
@@ -1690,7 +1701,7 @@ answer); @var{function} is a function of one argument (an object from
 
 When the user responds with @var{char}, @code{map-y-or-n-p} calls
 @var{function}.  If it returns non-@code{nil}, the object is considered
-``acted upon'', and @code{map-y-or-n-p} advances to the next object in
+``acted upon,'' and @code{map-y-or-n-p} advances to the next object in
 @var{list}.  If it returns @code{nil}, the prompt is repeated for the
 same object.
 
@@ -1826,7 +1837,6 @@ minibuffer.  If no minibuffer is active, it returns @code{nil}.
 @end defun
 
 @defun minibuffer-prompt-end
-@tindex minibuffer-prompt-end
 This function returns the current
 position of the end of the minibuffer prompt, if a minibuffer is
 current.  Otherwise, it returns the minimum valid buffer position.
@@ -1838,7 +1848,6 @@ prompt, if a minibuffer is current.  Otherwise, it returns zero.
 @end defun
 
 @defun minibuffer-contents
-@tindex minibuffer-contents
 This function returns the editable
 contents of the minibuffer (that is, everything except the prompt) as
 a string, if a minibuffer is current.  Otherwise, it returns the
@@ -1846,20 +1855,17 @@ entire contents of the current buffer.
 @end defun
 
 @defun minibuffer-contents-no-properties
-@tindex minibuffer-contents-no-properties
 This is like @code{minibuffer-contents}, except that it does not copy text
 properties, just the characters themselves.  @xref{Text Properties}.
 @end defun
 
 @defun minibuffer-completion-contents
-@tindex minibuffer-completion-contents
 This is like @code{minibuffer-contents}, except that it returns only
 the contents before point.  That is the part that completion commands
 operate on.  @xref{Minibuffer Completion}.
 @end defun
 
 @defun delete-minibuffer-contents
-@tindex delete-minibuffer-contents
 This function erases the editable contents of the minibuffer (that is,
 everything except the prompt), if a minibuffer is current.  Otherwise,
 it erases the entire current buffer.