From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: maintain flymake.el
Date: Mon, 16 Dec 2013 09:32:23 -0500 [thread overview]
Message-ID: <8738lsq32g.fsf@flea.lifelogs.com> (raw)
In-Reply-To: CALf2awQfQ+mJ63Wq3qN0pTAW-R9eCPAoz1n_Ep_=AKFrGOJQrQ@mail.gmail.com
On Sun, 15 Dec 2013 19:31:46 +0100 Sebastian Wiesner <lunaryorn@gmail.com> wrote:
SW> 2013/12/14 Sebastian Wiesner <lunaryorn@gmail.com>:
>> I hope to finish the document by tomorrow evening, and will come back
>> if it's done.
SW> I have completed the document now. The final version is to be found
SW> at https://github.com/flycheck/flycheck/wiki/Flycheck-versus-Flymake.
SW> It's a thorough write-up of the differences and similarities between
SW> Flycheck and Flymake, and probably also a comprehensive summary of the
SW> current issues and weaknesses in Flymake.
SW> Again, it's probably unfairly biased towards Flycheck. I tried my
SW> best to be neutral, but I consider Flycheck superior and think that
SW> the design and implementation of Flymake are somewhat broken, so I may
SW> have failed to properly account for Flymake's features and strengths.
SW> Please excuse this, and feel free to correct any mistakes I may have
SW> made.
SW> Please also suggest improvements, such as additional aspects which
SW> should be covered, or report issues, such as missing details in the
SW> comparsion.
I thought it was a thorough comparison. I'll let Leo, if he's willing,
answer any items.
We can't put Flycheck in Emacs as it stands, too many contributors
without copyright assignments. If precedent holds, I would expect the
Emacs project to continue endorsing Flymake despite its shortcomings
because of the licensing. Would you consider doing the necessary work
to make Flycheck part of Emacs?
Ted
next prev parent reply other threads:[~2013-12-16 14:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 17:01 maintain flymake.el Leo Liu
2013-12-06 17:38 ` Stefan Monnier
2013-12-06 17:50 ` Ted Zlatanov
2013-12-07 2:21 ` Leo Liu
2013-12-14 21:23 ` Sebastian Wiesner
2013-12-15 18:31 ` Sebastian Wiesner
2013-12-16 14:32 ` Ted Zlatanov [this message]
2013-12-16 16:06 ` Jan Djärv
2013-12-16 16:48 ` Sebastian Wiesner
2013-12-16 18:30 ` Jan Djärv
2013-12-16 19:03 ` Sebastian Wiesner
2013-12-16 16:57 ` Sebastian Wiesner
2013-12-16 17:26 ` Glenn Morris
2013-12-16 18:24 ` Sebastian Wiesner
2013-12-16 20:55 ` Glenn Morris
2013-12-16 21:00 ` Sebastian Wiesner
2013-12-16 21:30 ` Lennart Borgman
2013-12-16 21:52 ` Glenn Morris
2013-12-16 17:28 ` Ted Zlatanov
2013-12-17 0:12 ` Leo Liu
2013-12-17 0:02 ` Leo Liu
2013-12-17 6:37 ` Arne Jørgensen
2013-12-17 15:45 ` Leo Liu
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=8738lsq32g.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.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).