Re: Completion

[Lars Ingebrigtsen <larsi@gnus.org>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> +if there is one match, but it's not an exact match, the function
>> +should return the match;
>
> Actualy, when there is one match, "the common substring of all matches"
> is that match, so I think we can make it simpler, e.g.:
>
>     This specifies a @code{try-completion} operation.  The function should
>     return @code{t} if the specified string is a unique and exact match;
>     It should return @code{nil} if there are no matches; and it should
>     return the longest common prefix of all matches otherwise.

Yes, that seems clearer.

> What if the user writes the whole name by hand: how do you get the ID in
> this case?  In my experience, the need to handle that "manual case" most
> of the time ends up covering just as well the case where the user
> selected an entry from the *Completions*.

Oh, I didn't even consider that the user may type the name.  Yeah,
you're right; returning the text properties wouldn't really be generally
useful here...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no