From: Dmitry Gutov <dmitry@gutov.dev>
To: Philip Kaludercic <philipk@posteo.net>,
Bozhidar Batsov <bozhidar@batsov.dev>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Adding Flycheck to NonGNU ELPA
Date: Mon, 19 Feb 2024 21:32:27 +0200 [thread overview]
Message-ID: <b6c7b3f3-a91f-436d-b4b5-7eadc3d0810c@gutov.dev> (raw)
In-Reply-To: <87le7g9tg9.fsf@posteo.net>
On 19/02/2024 20:53, Philip Kaludercic wrote:
> To this end, I repeat my question: What_technical functionality_ does
> Flycheck_currently_ provide that Flymake does not? A different way of
> putting it is what architectural advantages does Flycheck exemplify over
> Flymake, that give it an inherent edge? If there aren't too many
> differences, I think the cost of confusion (Flymake and Flycheck are
> names that are easy to confuse) and of inducing choice-fatigue among new
> users is not something we should ignore.
I'm fairly sure the main answer is "lots of built-in checkers", much
more than flymake still has now.
It also has a minor mode map, to invoke the errors buffer or jump
between the errors. Though the latter is easy-ish to port over.
On the subject of choice fatigue, would we hesitate to include lsp-mode
in NonGNU ELPA, now that Eglot is in the core? I feel that would be the
wrong move.
next prev parent reply other threads:[~2024-02-19 19:32 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 [this message]
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
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=b6c7b3f3-a91f-436d-b4b5-7eadc3d0810c@gutov.dev \
--to=dmitry@gutov.dev \
--cc=bozhidar@batsov.dev \
--cc=emacs-devel@gnu.org \
--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).