Bug#1013298: maybe retire?
I'm actually wondering if it's worth working on flycheck at all at the
moment.
reading this post:
https://www.masteringemacs.org/article/spotlight-flycheck-a-flymake-replacement
I found this:
> So why switch away from Flymake? Well, before the advent of Emacs 27
> and the renewed interest in Flymake, I’d argue because Flymake had
> atrophied for a long time. Nowadays the distinction is less clear. If
> running M-x flymake-mode works as you expect – this is doubly true if
> you’re using a Language Server client like eglot or LSP-mode – then
> you can just stick with Flymake. It works well. But, if you’re using
> an older version of Emacs, or if you want a package with nearly a
> decade’s worth of attention lavished on it, you may want to give
> Flycheck a shot.
We're not "using an older version of Emacs", we're pretty good at
keeping up with upstream releases. So why should we bother with
Flycheck?
There's a comparison page that still seem to favor flycheck;
https://www.flycheck.org/en/latest/user/flycheck-versus-flymake.html
... but it hasn't been updated in 3 years, so I asked upstream for an
update:
https://github.com/flycheck/flycheck/issues/2023
I might also try to switch back to plain flymake myself.
a.
--
There is no power on earth from which we should be prepared to accept
an order to kill.
- Albert Einstein
Reply to: