From 6ecb21f15884aa592bac868c5d940c477b317573 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Wed, 18 Sep 1996 22:57:51 +0000 Subject: [PATCH] Clarify how completing-read returns an empty string. --- lispref/minibuf.texi | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) 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} -- 2.39.2