# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 843087471 0
# Node ID 75913ae7ac7e3017b3dafd99df8368922d659eeb
# Parent  4c9450bfc4db7e525c783fcd390a3142431d55f2
Clarify how completing-read returns an empty string.

diff -r 4c9450bfc4db -r 75913ae7ac7e lispref/minibuf.texi
--- a/lispref/minibuf.texi	Wed Sep 18 22:56:24 1996 +0000
+++ b/lispref/minibuf.texi	Wed Sep 18 22:57:51 1996 +0000
@@ -601,10 +601,11 @@
 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}