emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: on helm substantial differences - Re: [PATCH] Support "\n" in icompl


From: Jean Louis
Subject: Re: on helm substantial differences - Re: [PATCH] Support "\n" in icomplete-separator
Date: Thu, 12 Nov 2020 20:49:18 +0300
User-agent: Mutt/2.0 (3d08634) (2020-11-07)

* Eli Zaretskii <eliz@gnu.org> [2020-11-12 17:41]:
> > Date: Thu, 12 Nov 2020 12:13:23 +0300
> > From: Jean Louis <bugs@gnu.support>
> > Cc: Eli Zaretskii <eliz@gnu.org>, rudalics@gmx.at, spacibba@aol.com,
> >   monnier@iro.umontreal.ca, andreyk.mad@gmail.com, emacs-devel@gnu.org
> > 
> > Emacs completion is based on the minibuffer. Helm completion is based
> > on the completion window.
> 
> No, the default Emacs completion is also based on a separate window
> showing the completion candidates in a special buffer *Completions*,
> when there are more than one.  It is optional features like icomplete
> and ivy that use the minibuffer for showing the completion candidates.

That sentence above is meant that completion in plain Emacs is taking
place in the minibuffer. Words are expanding in the minibuffer and
words are completed in the minibuffer.

That separate window, as separate and important subject, is opened
during completion process is great feature and I hope icomplete will
adopt it.

Helm completion does not complete in mini buffer. One can write
anything in the mini buffer so words are not expanding in the
minibuffer. Instead person is making choice in the separate window. I
hope you see that.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]