Re: Bugs in newly added completion capabilities.

[Kim F. Storm]

Luc Teirlinck <address@hidden> writes:

> ELISP> (try-completion "b" '(aa bb))
> *** Eval error ***  Invalid function: (aa bb)
>
> Note that `try-completion' does not believe that aa is a function
> called with argument bb.  It believes that (aa bb) is an anonymous
> lambda expression.  It could know that it is not, because the car is
> not lambda.  (That is what the patch I sent did.  It checked whether
> the car was lambda.)

I agree that checking for lambda is better -- it makes the ordinary
cases work without hacks, so only in the case where lambda itself is
in the list, special attention is needed.

>
>    I agree, test-completion should be fixed.  Would you like
>    to fix that?
>
> There are several ways to do that.  The easiest one would probably be
> to make assoc-string be able to handle symbols as well as strings.
> But maybe that would be too radical?

It could break existing code if somebody already abuses assoc-string to
find a string in a mixed list of strings and symbols.

But I'd say it would be ok to change it as you suggest.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk