bug#18643: 25.0.50; elisp--expect-function-p

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> BTW, to improve on these behaviors, one approach is to take the
>> macro-expansion code used in elisp--local-variables and use it
>> "everywhere".  I.e. expand elisp--local-variables so it doesn't just
>> return the list of local vars, but also returns whether we're inside
>> a quote, or we're expecting a function, or we're expecting an expression.
> Is it possible to use weight or priority i.e. the context decided
> doesn't cut completion space to a subset but instead prioritise those
> fit into the context by putting them at the front.  Or find a way to
> allow other completions to show up when the input matches none of the
> subset.

Yes, we can do that with completion-table-in-turn.
Note that the elisp--local-variables is pretty precise, so it might not
be necessary.

> Also could we not force users to insert ` before any completion in
> strings or comments.

We could provide a config option, but I'd rather we don't offer those
completions by default.


        Stefan