Mercurial > emacs
changeset 16238:75913ae7ac7e
Clarify how completing-read returns an empty string.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Wed, 18 Sep 1996 22:57:51 +0000 |
| parents | 4c9450bfc4db |
| children | c196d1ded35c |
| files | lispref/minibuf.texi |
| diffstat | 1 files changed, 5 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- 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}