From: Thierry Volpiatto <thievol@posteo.net>
To: Philip Kaludercic <philipk@posteo.net>
Cc: joakim@verona.se, Dmitry Gutov <dmitry@gutov.dev>,
Bozhidar Batsov <bozhidar@batsov.dev>,
Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Adding Flycheck to NonGNU ELPA
Date: Thu, 22 Feb 2024 08:41:58 +0000 [thread overview]
Message-ID: <8734tksxex.fsf@posteo.net> (raw)
In-Reply-To: <87le7f1hlq.fsf@posteo.net> (Philip Kaludercic's message of "Tue, 20 Feb 2024 11:48:49 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
>> Let's remove Helm from NonGNU, then: its UI paradigm is also different
>> from the core Emacs, and IMHO it's rather ugly.
[Not sure who wrote this] but anyway,
saying a package is ugly just because it provides a different UI than
Emacs is unfair at best. Helm is and is still one of the best
completion package (but not only) around here and I made a lot of work
for this, so please be respectful of my work or provide constructive critics.
>> And swiper/ivy from ELPA, just because.
Same here, a very good package and there is a lot of work behind this, so...
> While I am not a fan of Helm, it was initially added to provide popular
> packages that a number of people appeared to want to use. Luckily these
> packages fall into the category of providing the front-end of a shared
> interface (completing-read; and that not without issues, because they
> tend to abuse completing-read's text expansion idea by focusing on
> narrowing and selecting). And yes, there are packages that have hard
> dependencies on Helm, but usually when people submit these kinds of
> packages, we at least mention the idea of trying to generalise them, so
> that the front- and back-end can be disentangled from one another.
Helm is providing a full support on Emacs completion mechanism
(completing-read, completion-in-region etc...), Emacs
styles included.
--
Thierry
next prev parent reply other threads:[~2024-02-22 8:41 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:51 Adding Flycheck to NonGNU ELPA Bozhidar Batsov
2024-02-19 17:44 ` Philip Kaludercic
2024-02-19 18:08 ` Bozhidar Batsov
2024-02-19 18:48 ` Eli Zaretskii
2024-02-19 19:18 ` Bozhidar Batsov
2024-02-19 18:53 ` Philip Kaludercic
2024-02-19 19:17 ` Bozhidar Batsov
2024-02-19 19:41 ` Philip Kaludercic
2024-02-19 19:32 ` Dmitry Gutov
2024-02-19 22:32 ` joakim
2024-02-20 11:48 ` Philip Kaludercic
2024-02-20 20:04 ` Dmitry Gutov
2024-02-21 14:38 ` Dmitry Gutov
2024-02-21 15:02 ` Stefan Monnier
2024-02-22 15:50 ` Dmitry Gutov
2024-02-22 16:57 ` Philip Kaludercic
2024-02-22 17:10 ` Dmitry Gutov
2024-02-22 17:29 ` Bozhidar Batsov
2024-02-23 16:07 ` Docs on ELPA (was Re: Adding Flycheck to NonGNU ELPA) Spencer Baugh
2024-02-23 16:13 ` Philip Kaludercic
2024-02-23 23:37 ` Adam Porter
2024-02-24 8:04 ` Philip Kaludercic
2024-02-25 12:32 ` Corwin Brust
2024-02-24 23:25 ` Stefan Monnier
2024-02-25 10:06 ` Philip Kaludercic
2024-02-21 17:01 ` Adding Flycheck to NonGNU ELPA Philip Kaludercic
2024-02-21 17:38 ` Dmitry Gutov
2024-02-21 18:05 ` Philip Kaludercic
2024-02-21 18:07 ` Dmitry Gutov
2024-02-21 18:14 ` Stefan Monnier
2024-02-21 21:19 ` Stefan Kangas
2024-02-21 21:46 ` Bozhidar Batsov
2024-02-21 23:39 ` Stefan Monnier
2024-02-22 9:15 ` Stefan Kangas
2024-02-22 3:16 ` Dmitry Gutov
2024-02-22 7:15 ` Bozhidar Batsov
2024-02-22 10:15 ` Steve Purcell
2024-02-22 11:54 ` Dmitry Gutov
2024-02-22 10:14 ` Steve Purcell
2024-02-22 14:29 ` Dmitry Gutov
2024-02-23 16:20 ` Spencer Baugh
2024-02-23 17:58 ` Eli Zaretskii
2024-02-23 21:09 ` Dmitry Gutov
2024-02-21 17:40 ` Stefan Monnier
2024-02-21 17:00 ` Philip Kaludercic
2024-02-21 18:19 ` Dmitry Gutov
2024-02-21 21:24 ` Bozhidar Batsov
2024-02-22 8:41 ` Thierry Volpiatto [this message]
2024-02-22 11:57 ` Dmitry Gutov
2024-02-22 9:03 ` Po Lu
2024-02-19 19:33 ` Dmitry Gutov
2024-02-19 19:47 ` Bozhidar Batsov
2024-02-19 19:55 ` Dominik Schrempf
2024-02-19 23:21 ` Dmitry Gutov
2024-02-20 6:17 ` Bozhidar Batsov
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=8734tksxex.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=bozhidar@batsov.dev \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=philipk@posteo.net \
/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).