From: joaotavora@gmail.com (João Távora)
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Flymake support for C/C++
Date: Wed, 18 Oct 2017 15:26:21 +0100 [thread overview]
Message-ID: <878tg8jzw2.fsf@gmail.com> (raw)
In-Reply-To: <c3f12584-2137-9be6-ab0b-769cff80413b@gmail.com> ("Clément Pit-Claudel"'s message of "Wed, 18 Oct 2017 08:22:29 -0400")
Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
> On 2017-10-14 12:29, João Távora wrote:
>>> On 14 October 2017 at 09:00, Eli Zaretskii <eliz@gnu.org> wrote:
>>> See
>>> http://www.flycheck.org/en/latest/user/flycheck-versus-flymake.html#flycheck-versus-flymake
>>>
>>
>> That page is now completely outdated [...] please don't advertise a
>> misleading comparison.
>
> That's a strong statement, and I don't think it's fair: this page is
> intended to help users chose between Flycheck and Flymake *now*.
I don't know if we agree, but to me, "misleading" is not the same as
"ill-intentioned": I don't think I in any way implied that the page, its
authors or its proponents are or have ever been ill-intentioned (and for
the record, I don't believe so).
I just don't think it makes any sense to advertise that comparison
and/or to make any decisions based on it right now. You must agree that
decisions are things that affect the future and that when they are based
on outdated information, they have a higher probability of being
misled. So that's why I characterized the page as "misleading" and
that's why I politely asked Reuben to stop advertising it.
> Your Flymake update hasn't been released yet, so an update to that
> page comparing against the unreleased Flymake would mislead readers
> into thinking that Flymake can do more for them that it really can at
> this point.
I also didn't ask anyone to update the page, though I volunteered to
help. Again, I just asked to stop advertising it as a decision-making
premise and explained why.
> We do have a serious interest in updating it :) Could you help?
I can certainly fill in the gaps that aren't clear from the Flymake
manual, if you have already read it.
> I'd love to mention that a new release of FLymake, fixing most of
> these deficiencies, is in the works.
I think that this very phrase added somewhere visible is just fine, with
optional love of course :-)
João
next prev parent reply other threads:[~2017-10-18 14:26 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 15:09 [PATCH] Flymake support for C/C++ João Távora
2017-10-12 15:50 ` Mark Oteiza
2017-10-12 17:50 ` Alan Mackenzie
2017-10-12 18:45 ` Stefan Monnier
2017-10-12 20:45 ` Alan Mackenzie
2017-10-12 21:03 ` Stefan Monnier
2017-10-13 6:28 ` Eli Zaretskii
2017-10-12 18:46 ` João Távora
2017-10-12 20:39 ` Alan Mackenzie
2017-10-12 21:05 ` Stefan Monnier
2017-10-12 21:24 ` João Távora
2018-06-01 21:07 ` Alan Mackenzie
2018-06-01 21:54 ` João Távora
2018-06-01 22:08 ` Stefan Monnier
2018-06-01 23:23 ` Rolf Ade
2018-06-02 10:33 ` Alan Mackenzie
2018-06-02 14:44 ` Stefan Monnier
2018-06-02 18:13 ` João Távora
2018-06-03 15:45 ` Alan Mackenzie
2018-06-03 16:28 ` João Távora
2018-06-03 16:43 ` Alan Mackenzie
2018-06-03 17:02 ` João Távora
2018-06-02 17:16 ` Stefan Monnier
2018-06-02 15:26 ` Stefan Monnier
2018-06-03 13:44 ` Alan Mackenzie
2017-10-14 1:34 ` Richard Stallman
2017-10-14 7:10 ` Reuben Thomas
2017-10-14 7:58 ` Sami Kerola
2017-10-14 8:00 ` Eli Zaretskii
2017-10-14 8:15 ` Reuben Thomas
2017-10-14 8:22 ` Dmitry Gutov
2017-10-14 8:29 ` Reuben Thomas
2017-10-14 10:36 ` Eli Zaretskii
2017-10-14 11:22 ` Reuben Thomas
2017-10-14 8:33 ` Eli Zaretskii
2017-10-17 10:53 ` Phillip Lord
2017-10-17 10:56 ` Reuben Thomas
2017-10-18 4:03 ` Richard Stallman
2017-10-18 10:18 ` Reuben Thomas
2017-10-19 3:26 ` Richard Stallman
2017-10-19 7:38 ` Reuben Thomas
2017-10-22 23:18 ` Richard Stallman
2017-10-22 23:23 ` Reuben Thomas
2017-10-24 4:12 ` Richard Stallman
2017-10-24 9:45 ` Reuben Thomas
2017-10-24 9:48 ` Dmitry Gutov
2017-10-24 9:52 ` Reuben Thomas
2017-10-24 9:57 ` Dmitry Gutov
2017-10-24 10:07 ` Reuben Thomas
2017-10-24 10:21 ` Dmitry Gutov
2017-10-24 10:28 ` Reuben Thomas
2017-10-24 15:44 ` Stefan Monnier
2017-10-25 19:30 ` Richard Stallman
2017-10-27 0:43 ` Reuben Thomas
2017-10-28 21:47 ` Richard Stallman
2017-10-18 12:16 ` Clément Pit-Claudel
2017-10-18 17:30 ` John Wiegley
2017-10-14 13:55 ` Stefan Monnier
2017-10-14 9:33 ` João Távora
2017-10-14 10:56 ` guillaume papin
2017-10-14 16:29 ` João Távora
2017-10-14 16:36 ` Reuben Thomas
2017-10-18 12:22 ` Clément Pit-Claudel
2017-10-18 14:26 ` João Távora [this message]
2017-10-14 9:29 ` João Távora
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=878tg8jzw2.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
/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).