From 4d19f455abd5293ce4a96a0e189203cd7766ecd1 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sat, 20 Nov 2004 22:08:39 +0000 Subject: [PATCH] (Text from Minibuffer): Document KEEP-ALL arg in read-from-minibuffer. --- lispref/minibuf.texi | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi index 3ac750d76a1..1455c63fe34 100644 --- a/lispref/minibuf.texi +++ b/lispref/minibuf.texi @@ -118,7 +118,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 +@defun read-from-minibuffer prompt-string &optional initial-contents keymap read hist default inherit-input-method keep-all 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 @@ -170,6 +170,9 @@ 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}. -- 2.39.2