From: joaotavora@gmail.com (João Távora)
To: emacs-devel@gnu.org, eliz@gnu.org, sdl.web@gmail.com,
monnier@iro.umontreal.ca
Subject: New Flymake rewrite in emacs-26
Date: Tue, 03 Oct 2017 15:05:44 +0100 [thread overview]
Message-ID: <8760bwz5qf.fsf@gmail.com> (raw)
Hi,
As discussed, I have just merged the Flymake rewrite into emacs-26. I
did this sooner than I expected so people can give it as much testing as
possible.
`flymake-mode' is not active by default, so when writing Elisp, I
encourage you to try out the new backends. Just M-x flymake-mode or
(add-to-list 'emacs-lisp-mode-hook 'flymake-mode).
Of course if you were already using Flymake for C, C++, etc. Everything
should also still work (slightly better, in fact). Let me know if it
doesn't.
Some things worth noting:
* There are two older commits in emacs-26 that must be merged to master
after all, otherwise the merge-back of this feature won't work.
This is because there was a reversion of the decision to bring this
feature to emacs-26 (see
https://lists.gnu.org/archive/html/emacs-devel/2017-09/msg01020.html
and
https://lists.gnu.org/archive/html/emacs-devel/2017-09/msg01030.html)
the reversion
The two commits are
ce540f8a68..: João Távora 2017-09-27 Revert "Split flymake.el into flymake-proc.el and flymake-ui.el"
7cf59c6635..: João Távora 2017-09-27 Revert "Add flymake-backends defcustom"
* The most important docstrings are in place, but the Texinfo
documentation (which I also rewrote considerably) is missing the bits
about the new API for writing backends.
Ideally, I would like some feedback on it (besides Stefan, of
course). Please see the docstrings of `flymake-diagnostic-functions'
and `flymake-diagnostic-types-alist'.
Even more ideally, someone would write a nicer backend for Emacs's C
sources (the current "legacy" one requires Makefiles to contain a
"syntax-check" target, which isn't practical, I presume)
Thanks,
João
next reply other threads:[~2017-10-03 14:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 14:05 João Távora [this message]
2017-10-03 15:00 ` New Flymake rewrite in emacs-26 Eli Zaretskii
2017-10-04 11:58 ` Lele Gaifax
2017-10-04 13:41 ` Lele Gaifax
2017-10-04 16:08 ` João Távora
2017-10-04 16:42 ` Lele Gaifax
2017-10-04 18:11 ` Lele Gaifax
2017-10-05 2:21 ` João Távora
2017-10-05 11:42 ` Lele Gaifax
2017-10-05 23:32 ` Noam Postavsky
2017-10-06 13:16 ` João Távora
2017-10-06 13:24 ` Noam Postavsky
2017-10-06 15:48 ` João Távora
2017-10-07 7:37 ` Lele Gaifax
2017-10-07 16:08 ` João Távora
2017-10-10 12:25 ` João Távora
2017-10-10 14:18 ` Eli Zaretskii
2017-10-10 15:09 ` João Távora
2017-10-10 15:53 ` Eli Zaretskii
2017-10-10 16:25 ` João Távora
2017-10-10 16:40 ` Eli Zaretskii
2017-10-10 17:03 ` João Távora
2017-10-10 17:20 ` Noam Postavsky
2017-10-11 0:07 ` João Távora
2017-10-11 0:59 ` Noam Postavsky
2017-10-11 10:39 ` Eli Zaretskii
2017-10-11 12:16 ` Noam Postavsky
2017-10-11 12:25 ` João Távora
2017-10-11 10:24 ` Eli Zaretskii
2017-10-11 12:01 ` João Távora
2017-10-11 12:13 ` Eli Zaretskii
2017-10-11 13:41 ` João Távora
2017-10-11 17:49 ` Romanos Skiadas
2017-10-11 18:39 ` guillaume papin
2017-10-12 13:17 ` João Távora
2017-10-11 20:25 ` Stefan Monnier
2017-10-12 13:10 ` João Távora
2017-10-12 13:43 ` Stefan Monnier
2017-10-12 13:56 ` João Távora
2017-10-11 13:11 ` Mark Oteiza
2017-10-10 17:23 ` Eli Zaretskii
2017-10-11 11:11 ` Lele Gaifax
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=8760bwz5qf.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sdl.web@gmail.com \
/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.