From: Richard M. Stallman <rms@gnu.org>
Date: Wed, 18 Sep 1996 22:57:51 +0000 (+0000)
Subject: Clarify how completing-read returns an empty string.
X-Git-Tag: emacs-20.1~3706
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=6ecb21f15884aa592bac868c5d940c477b317573;p=emacs.git

Clarify how completing-read returns an empty string.
---

diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index f1d2569a466..36e976dbcb7 100644
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -601,10 +601,11 @@ commands won't exit unless the input typed is itself an element of
 commands work regardless of the input in the minibuffer.
 
 The user can exit with null input by typing @key{RET} with an empty
-minibuffer.  Then @code{completing-read} returns @code{nil}.  This is
-how the user requests whatever default the command uses for the value
-being read.  The user can return using @key{RET} in this way regardless
-of the value of @var{require-match}.
+minibuffer.  Then @code{completing-read} returns @code{""}.  This is how
+the user requests whatever default the command uses for the value being
+read.  The user can return using @key{RET} in this way regardless of the
+value of @var{require-match}, and regardless of whether the empty string
+is included in @var{collection}.
 
 The function @code{completing-read} works by calling
 @code{read-minibuffer}.  It uses @code{minibuffer-local-completion-map}