From: "João Távora" <joaotavora@gmail.com>
To: Mohsin Kaleem <mohkale@kisara.moe>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>,
emacs-devel@gnu.org
Subject: Re: [ELPA] Add package flymake-rest
Date: Fri, 21 Apr 2023 18:43:36 +0100 [thread overview]
Message-ID: <CALDnm52Q=CMsrEhY0te7MsE2hRj6PiE_Gua5Jh4eEn9sf3Mn_A@mail.gmail.com> (raw)
In-Reply-To: <87wn255n8a.fsf@kisara.moe>
On Fri, Apr 21, 2023 at 4:06 PM Mohsin Kaleem <mohkale@kisara.moe> wrote:
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> Hi all,
>
> Just to give a quick update. I've started work on a new functional
> framework for flymake-collections checkers. Once it's ready I'll
> probably re-approach the matter of ELPA or perhaps even builtin
> flymake support for it.
If that functional framework is well design and generally
useful (it could -- ideally should -- help in simplifying
the few Flymake backends that are already in core) then
we can add it to lisp/progmodes/flymake.el.
Flymake is a :core ELPA package, meaning you could submit that
change to the master branch and it would soon be accessible to
other ELPA packages. Then your flymake-rest package could just
depend on this new version of Flymake and so could other packages
like Eglot (of course, only if the change were actually beneficial to it).
TL;DR In general, if you see yourself typing any code that
could help Flymake elsewhere in other contexts, consider
submitting that code to lisp/progmodes/flymake.el
João
next prev parent reply other threads:[~2023-04-21 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 8:34 [ELPA] Add package flymake-rest Mohsin Kaleem
2022-05-08 10:06 ` Philip Kaludercic
2022-05-08 10:17 ` Mohsin Kaleem
2022-05-08 19:09 ` Philip Kaludercic
2022-05-08 21:52 ` Stefan Monnier
2023-04-21 14:22 ` Mohsin Kaleem
2023-04-21 17:43 ` João Távora [this message]
2023-04-22 6:51 ` Philip Kaludercic
2023-04-22 10:27 ` Mohsin Kaleem
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='CALDnm52Q=CMsrEhY0te7MsE2hRj6PiE_Gua5Jh4eEn9sf3Mn_A@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mohkale@kisara.moe \
--cc=monnier@iro.umontreal.ca \
--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).