From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Oleh Krehel <ohwoeowho@gmail.com>
Cc: Ergus <spacibba@aol.com>,
"Andrea Corallo via Emacs development discussions."
<emacs-devel@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>,
Andrea Corallo <akrl@sdf.org>
Subject: Re: Include ivy + counsel in Emacs core?
Date: Thu, 05 Nov 2020 00:31:13 +0000 [thread overview]
Message-ID: <87y2jglk4u.fsf@tcd.ie> (raw)
In-Reply-To: <b2f9a36d-9aed-aa87-0bf1-ad66b8eb7f7a@gmail.com> (Oleh Krehel's message of "Mon, 14 Sep 2020 13:12:36 +0200")
Oleh Krehel <ohwoeowho@gmail.com> writes:
> On 9/13/20 11:26 PM, Ergus wrote:
>> On Sun, Sep 13, 2020 at 04:36:13PM -0400, Stefan Monnier wrote:
>>> 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) ;-(
>>>
>>>
>>> Stefan
>>>
>> An important part of ivy was re-implemented the last year to simplify
>> and unify some interfaces and many errors were corrected.
>>
>> I use ivy since 4 years ago with not big issues for the moment (When I
>> have them I have reported and they have been solved almost immediately).
>> But it needs some improve before becoming part of vanilla.
>>
>> It would be very nice if you comment/report/ask that to Abo-Abo. To get
>> an update of the current status.
>
> I'm eager to solve the problems with completion tables. Some of them should
> already be solved.
>
> If there was a bug report with a reproducible scenario, that would make things
> move faster.
See e.g. https://github.com/abo-abo/swiper/issues/1597 for an issue with
programmed completion.
--
Basil
next prev parent reply other threads:[~2020-11-05 0:31 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 [this message]
2020-11-05 0:34 ` Basil L. Contovounesios
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2jglk4u.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 \
--cc=spacibba@aol.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).