Subject: Re: bug#21644: 24.4; completing-read acts differently on functional collection

From: Ryan <[email-masked]>
Date: Wed, 14 Oct 2015 22:17:54 -0700

On 10/14/15 10:12 PM, Dmitry Gutov wrote:
> On 10/13/2015 09:59 PM, Ryan C. Thompson wrote:
>
>>> (info "(elisp) Programmed Completion") or
>>> (info "(elisp) Basic Completion"), probably.
>> Maybe the `completing-read' docstring should link to these info nodes.
>
> This seems like it should suffice. Do you agree?
>
> diff --git a/src/minibuf.c b/src/minibuf.c
> index 4e5c17d..2cde8b0 100644
> --- a/src/minibuf.c
> +++ b/src/minibuf.c
> @@ -1595,7 +1595,7 @@ PROMPT is a string to prompt with; normally it 
> ends in a colon and a space.
>  COLLECTION can be a list of strings, an alist, an obarray or a hash 
> table.
>  COLLECTION can also be a function to do the completion itself.
>  PREDICATE limits completion to a subset of COLLECTION.
> -See `try-completion' and `all-completions' for more details
> +See Info node `(elisp)Basic Completion' for more details
>   on completion, COLLECTION, and PREDICATE.
>
>  REQUIRE-MATCH can take the following values:
>
Yes, I think that should be fine. That would have certainly solved the 
problem in my case, since I would have known to implement the 
`test-completion' case.