From: Juri Linkov <juri@jurta.org>
Date: Thu, 25 May 2006 22:57:50 +0000 (+0000)
Subject: (Text from Minibuffer): Undocument keep-all.
X-Git-Tag: emacs-pretest-22.0.90~2317
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=63d336640effbaa2ebc6d217bc70819d0897e595;p=emacs.git

(Text from Minibuffer): Undocument keep-all.
---

diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index f69cf03deac..2fca6cc04b8 100644
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -110,7 +110,7 @@ middle of a Lisp function.  Instead, do all minibuffer input as part of
 reading the arguments for a command, in the @code{interactive}
 specification.  @xref{Defining Commands}.
 
-@defun read-from-minibuffer prompt-string &optional initial-contents keymap read hist default inherit-input-method keep-all
+@defun read-from-minibuffer prompt-string &optional initial-contents keymap read hist default inherit-input-method
 This function is the most general way to get input through the
 minibuffer.  By default, it accepts arbitrary text and returns it as a
 string; however, if @var{read} is non-@code{nil}, then it uses
@@ -162,9 +162,6 @@ the setting of @code{enable-multibyte-characters} (@pxref{Text
 Representations}) from whichever buffer was current before entering the
 minibuffer.
 
-If @var{keep-all} is non-@code{nil}, even empty and duplicate inputs
-are added to the history list.
-
 Use of @var{initial-contents} is mostly deprecated; we recommend using
 a non-@code{nil} value only in conjunction with specifying a cons cell
 for @var{hist}.  @xref{Initial Input}.