[Top][All Lists]

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

RE: Include ivy + counsel in Emacs core?

From: arthur miller
Subject: RE: Include ivy + counsel in Emacs core?
Date: Sun, 13 Sep 2020 20:13:24 +0000

I have used ivy+counsel for about some year or so for quite some time ago, but I have since switched to Helm and have been using it for like maybe years now.  In my opinion it is less buggy, has better and more integration with other packages and also feels for some reason more straightforward than Ivy and counsel.

In that case I would probably  vote for Helm,  but I am completely happy with such big packages being out of Emacs core. I would even like to see Org being left out or at least demoted to Elpa.

-------- Originalmeddelande --------
Från: Ricardo Wurmus <rekado@elephly.net>
Datum: 2020-09-13 21:13 (GMT+01:00)
Till: Andrea Corallo <akrl@sdf.org>
Kopia: Oleh Krehel <ohwoeowho@gmail.com>, emacs-devel@gnu.org
Ämne: Re: Include ivy + counsel in Emacs core?

Andrea Corallo via Emacs development discussions. <emacs-devel@gnu.org> writes:

> was ever considered the inclusion of ivy + counsel in the Emacs core
> distribution?
> ivy+counsel it's a quality package that reached already noticeable
> popularity.  Does fuzzy completion with vertical output display, and its
> counsel-M-X shows also the command key binding (feature I consider for
> my experience a _game changer_ for softening the learning curve).
> Finally it's already in ELPA.

As someone who has used ivy for several months I should note that it
doesn’t work well with “M-x rgrep” (it tries to complete files when
asked for a pattern); see also

There are also a couple of things that might trip up new users, for
example the need to hit C-j to confirm a new file name instead of
selecting a similar matching file name (which is what RET gives you).

While I think it’s pretty nice in general (and I do prefer it over Helm)
and an improvement over the default of no completion, I do feel it’s a
little … invasive or coercive in that it’s a bit awkward to bypass it.


reply via email to

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