RE: [External] : Re: Add completion to compilation-read-command

[Drew Adams]

> >> There were many proposals how to implement `eager-update' to update
> >> *Completions* as you type.  We just need to put together all parts.
> >
> > Taking me back...
> > Icicles has had all of that since 2006.
> >
> > https://www.emacswiki.org/emacs/Icicles_-_History_Enhancements
> >
> > https://www.emacswiki.org/emacs/Icicles_-_Nutshell_View*ProgressiveCompletion
> >
> > https://www.emacswiki.org/emacs/Icicles_-_Nutshell_View*ChippingAway
> >
> > https://www.emacswiki.org/emacs/Icicles_-_Icompletion*IncrementalCompletion
> >
> > https://www.emacswiki.org/emacs/Icicles_-_Progressive_Completion
> 
> Thanks for the references.  Incremental and Progressive Completions
> look similar.

Similar to what?  Not similar to each other.

I call "incremental completion" (or icompletion)
the automatic or on-demand updating of matches
as you edit your input pattern.

I call "progressive completion" the ability to
(repetitively) match/filter the current set of
completion candidates with an additional pattern,
i.e., updating the candidate set each time.

Icicles can use a recursive minibuffer for any
pattern, so you can return up one or more edit
levels to match another pattern there.