From: Ergus <spacibba@aol.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Flymake backends
Date: Sun, 16 Apr 2023 22:35:57 +0200 [thread overview]
Message-ID: <vqwnrpu4jcbzcas42zbmq4fywfqjatykn2amefy5frlbgdhapa@ud2puuarinzs> (raw)
In-Reply-To: <87wn2btz63.fsf@posteo.net>
Hi Philip:
On Sun, Apr 16, 2023 at 07:17:08PM +0000, Philip Kaludercic wrote:
>Ergus <spacibba@aol.com> writes:
>
>
>There has been an attempt at abstracting over the current API in this
>project: https://github.com/mohkale/flymake-collection
>
Thanks for replying. I am looking the flymake-collection project and I
think that this is the kind of api we should offer to the user for
applications development. Even that one or a simplified version of that.
But sadly the project is not in elpa... so what should we do for that?
>> Because there are multiple functions the flymake code to simplify common
>> tasks, but they are intended for private use cases.
>>
>> It may simplify integration with other build systems like ninja or
>> cmake.
>>
>> So far something like flymake-quickdef, may help...
>>
>> 2) Is it desirable to add built-in backends to flymake for common/simple
>> tools generally available like cppcheck, flake and so on... to improve
>> the default experience and minimize configuration?
>
>I think that is of interest. In Emacs 29 shellcheck was added for
>instance, and I don't see why other systems shouldn't be supported
>either (setting aside legal issues).
>
Then I think we should first provide a simpler api that we can maintain
better (i.e. bring functions like flymake-collection-define-rx to
vanilla)
And then we can make a list of the common backends we can support:
So far we only need to give a look to the backends supported by flycheck.
>> Best,
>> Ergus
next prev parent reply other threads:[~2023-04-16 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hsryxz6ppcdsvv7i2ebdwoimldlg5b7xewgh43vz2jbbjsqe6d.ref@o6naxb3fkymi>
2023-04-16 15:07 ` Flymake backends Ergus
2023-04-16 19:17 ` Philip Kaludercic
2023-04-16 20:35 ` Ergus [this message]
2023-04-17 13:21 ` Philip Kaludercic
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=vqwnrpu4jcbzcas42zbmq4fywfqjatykn2amefy5frlbgdhapa@ud2puuarinzs \
--to=spacibba@aol.com \
--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).