all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andrea Corallo <akrl@sdf.org>, Oleh Krehel <ohwoeowho@gmail.com>,
	"Andrea Corallo via Emacs development discussions."
	<emacs-devel@gnu.org>
Subject: Re: Include ivy + counsel in Emacs core?
Date: Thu, 05 Nov 2020 00:34:45 +0000	[thread overview]
Message-ID: <87r1p8ljyy.fsf@tcd.ie> (raw)
In-Reply-To: <jwvzh5t5shx.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 13 Sep 2020 16:36:13 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> 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.
>
> Last I heard Ivy still had problems with some completion tables (IIRC
> with those completion tables that return non-trivial values from
> `completion-boundaries`, such as the completion table used for
> filenames, tho there might be other issues such as the support for
> unquote/requote).  If that's still the case (it was several years ago),
> then enabling Ivy by default would either introduce regressions when
> completing against such completion tables, or would force us to use
> 2 different UIs (the Ivy one where it works well, as some other UI for
> those other cases) ;-(

I don't think anyone's suggesting enabling it by default.  But then,
given that it's already in GNU ELPA, I'm not sure what would be gained
from putting it in core, other than greater exposure to the experts on
emacs-devel and bug-gnu-emacs.

-- 
Basil



  parent reply	other threads:[~2020-11-05  0:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 18:53 Include ivy + counsel in Emacs core? Andrea Corallo via Emacs development discussions.
2020-09-13 19:14 ` Ricardo Wurmus
2020-09-13 20:13   ` arthur miller
2020-09-13 20:25     ` ej32u--- via Emacs development discussions.
2020-09-13 20:32       ` Doug Davis
2020-09-13 21:00       ` arthur miller
2020-09-13 20:36 ` Stefan Monnier
2020-09-13 21:26   ` Ergus
2020-09-14  6:15     ` Andrea Corallo via Emacs development discussions.
2020-09-14 11:12     ` Oleh Krehel
2020-11-05  0:31       ` Basil L. Contovounesios
2020-11-05  0:34   ` Basil L. Contovounesios [this message]
2020-09-13 21:32 ` Dmitry Gutov
2020-09-14 11:09   ` Oleh Krehel
2020-09-14 22:58     ` Dmitry Gutov
2020-09-14 11:16 ` Oleh Krehel
  -- strict thread matches above, loose matches on Subject: below --
2020-09-14  2:36 Jai Flack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1p8ljyy.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=akrl@sdf.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=ohwoeowho@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.