From: Dmitry Gutov <dmitry@gutov.dev>
To: Stefan Kangas <stefankangas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>
Cc: joakim@verona.se, Bozhidar Batsov <bozhidar@batsov.dev>,
Emacs Devel <emacs-devel@gnu.org>,
Steve Purcell <steve@sanityinc.com>
Subject: Re: Adding Flycheck to NonGNU ELPA
Date: Thu, 22 Feb 2024 05:16:45 +0200 [thread overview]
Message-ID: <553db84b-e29b-4622-a02d-77e250f2d1d2@gutov.dev> (raw)
In-Reply-To: <CADwFkmmnEpzn77+=ZpiLPxoRpa1PCpSy3p+=7WXnto+n-hXxPw@mail.gmail.com>
On 21/02/2024 23:19, Stefan Kangas wrote:
> Another thing is that we could use a good built-in macro to define
> flymake backends.
>
> Perhaps Steve Purcell (added to CC) could be convinced to contribute his
> excellent flymake-flycheck[2] and flymake-easy[3] packages to core?
> This would kill two (or more) birds with one stone, and also remove some
> of the gripes that some users have with flymake.
There doesn't seem much point in having flymake-flycheck in the core
when flycheck is still required to use most of its backends (they're
part of the package). It also depends on flycheck at runtime anyway.
flymake-easy has another problem: IIUC it hasn't been updated for 10
years, and as such only uses the obsolete Flymake protocol (one we keep
in flymake-proc.el for compatibility). It also employs defadvice.
Back to flymake-flycheck, I wonder if it would be a better idea to have
it as part of the flycheck package itself (fewer things to install and
enable separately). But then it's not obvious at which point the
checkers should be made available to flymake. If that happens when
flycheck-mode is enabled, that would be too late: at that point the user
has seemingly indicated that they want to use flycheck as UI as well.
> [2] https://github.com/purcell/flymake-flycheck
>
> [3] https://github.com/purcell/flymake-easy
next prev parent reply other threads:[~2024-02-22 3:16 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 [this message]
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=553db84b-e29b-4622-a02d-77e250f2d1d2@gutov.dev \
--to=dmitry@gutov.dev \
--cc=bozhidar@batsov.dev \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
--cc=steve@sanityinc.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).