From: arthur miller <arthur.miller@live.com>
To: "ej32u@pm.me" <ej32u@pm.me>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Include ivy + counsel in Emacs core?
Date: Sun, 13 Sep 2020 21:00:15 +0000 [thread overview]
Message-ID: <VI1PR06MB4526F6C984C5769256DDC2C796220@VI1PR06MB4526.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <30de6179-dc56-abbb-3bb4-fe9c497e7aaf@pm.me>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Oki, that was news for me. Let us hope Thierry will change his mind and continue or someone else will help.
I remember that he announced some time ago that he will maybe stop developing Helm due to lack of time and resource.
-------- Originalmeddelande --------
Från: "ej32u--- via Emacs development discussions." <emacs-devel@gnu.org>
Datum: 2020-09-13 22:26 (GMT+01:00)
Till: emacs-devel@gnu.org
Ämne: Re: Include ivy + counsel in Emacs core?
On 9/13/20 4:13 PM, arthur miller wrote:
> 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.
I believe the Helm maintainer no longer wishes to work on Helm (see here:
https://github.com/emacs-helm/helm/issues/2386).
[-- Attachment #2: Type: text/html, Size: 2042 bytes --]
next prev parent reply other threads:[~2020-09-13 21:00 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 [this message]
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
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=VI1PR06MB4526F6C984C5769256DDC2C796220@VI1PR06MB4526.eurprd06.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=ej32u@pm.me \
--cc=emacs-devel@gnu.org \
/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).