From: Dmitry Gutov <dmitry@gutov.dev>
To: Philip Kaludercic <philipk@posteo.net>
Cc: joakim@verona.se, Bozhidar Batsov <bozhidar@batsov.dev>,
Emacs Devel <emacs-devel@gnu.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: Adding Flycheck to NonGNU ELPA
Date: Wed, 21 Feb 2024 19:38:55 +0200 [thread overview]
Message-ID: <706be920-cbd4-42d8-8c76-3abdb7e7b026@gutov.dev> (raw)
In-Reply-To: <87zfvtwy2w.fsf@posteo.net>
On 21/02/2024 19:01, Philip Kaludercic wrote:
> Dmitry Gutov<dmitry@gutov.dev> writes:
>
>> On 20/02/2024 22:04, Dmitry Gutov wrote:
>>> On 20/02/2024 13:48, Philip Kaludercic wrote:
>>>
>>>> If Flycheck were to use the same interface as Flymake, then the
>>>> situation would be better, as it would only be a different UI with
>>>> perhaps some other priorities.
>>> Flycheck uses macros to define checkers and output parsers. Perhaps
>>> one day those could expand to Flymake's functional interface under
>>> the covers, but for that to happen, it would help a lot if we were
>>> more welcoming.
>> So, unless unless there is a strong objection from one of Emacs's head
>> maintainers, I think I will commence Flycheck's addition to NonGNU in
>> the next few days.
> Before taking this step, can we please discuss the possibility of
> creating a uniform interface? As mentioned in my previous message, this
> is the crux of my complaint, and I don't even know what Bozhidar
> position on the matter is.
We've discussed it. Such possibility exists.
If we're going to make the implementation of it as a prerequisite for
merging, however, I imagine that's just not going to happen. Flycheck's
contributors will go back to their own bubble, and we'll stay in ours.
Those are my expectations both from experience, and from the current
mood of the people involved.
next prev parent reply other threads:[~2024-02-21 17:38 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=706be920-cbd4-42d8-8c76-3abdb7e7b026@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 \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.