Re: completion oddity

[Greg Klanderman <gak@xxxxxxxxxxxxxx>]

>>>>> On May 22, 2012 Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:

> You're right; in the first case the completion system has recorded a
> list of "ambiguous positions" that distinguish what it filled in vs.
> what the user typed.  It decides whether the match is unique based on
> whether there is another ambiguous position to which it can advance.
> This is all part of the aforementioned smarts.

Oh the horrors never end.. could you be so kind as to point me to some
of the relevant bits of code that are doing this logic and how that
state is stored?  Please tell me it's not in the even more
impenetrable C code..

Greg