Re: Completion with (:exclusive 'no) is called twice, and doesn't pass over on sole completion.

[Lennart Borgman]

On Sat, Mar 17, 2012 at 23:34, Stefan Monnier <address@hidden> wrote:
>>> Not sure why, but not terribly problematic either.
>> Right, unless the completion retrieval is computationally intensive.
>
> That could be a problem, but I haven't seen a circumstance where this is
> the case yet.  This computation is only meant to decide which completion
> table to use at a given buffer position.  The exact set of candidates
> can be computed later.

If a parser is involved to make the candidate it can of course take long time.