From: joaotavora@gmail.com (João Távora)
To: emacs-devel@gnu.org, dgutov@yandex.ru, sdl.web@gmail.com,
monnier@iro.umontreal.ca, jwiegley@gmail.com
Subject: Flymake refactored
Date: Thu, 28 Sep 2017 15:27:44 +0100 [thread overview]
Message-ID: <87h8vmj3tr.fsf@lolita> (raw)
[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]
Hi all,
I think my Flymake refactoring/rewriting effort is nearing
completion. Obviously people to take a look at it before it is
merged to master.
Here are the main changes:
* Flymake now annotates arbitrary buffer regions, not just lines.
* Flymake supports arbitrary diagnostic types, not just errors and
warnings. See variable flymake-diagnostic-types-alist.
* There is a clean separation between the UI showing the diagnostics
and the sources of these diagnostics, called backends.
* Flymake supports multiple simultaneous backends, meaning that you can
check your buffer from different perspectives.
* The "legacy" regexp-based backend still works nicely in my (limited)
testing. It is enabled by default but lives in a separate file
lisp/progmodes/flymake-proc.el
* Two backends for Emacs-lisp are provided in
lisp/progmodes/flymake-elisp.el. Enabling flymake-mode in an elisp
buffer should activate them.
* Backends are just functions kept in a buffer-local variable. See
flymake-diagnostic-functions.
* Some colorful fanciness in the mode-line. Still far from flycheck's
(which is very good) but should be easy to get there.
* In a separate scrap-able commit I bind M-n and M-p in flymake-mode to
navigate errors. I like it and the keys were unused, but it's probably
against the rules.
* I started rewriting the manual, but won't go much further until the
implementation is stabilized.
Regarding backward compatibility:
* I have provided obsolete aliases for most variables and functions,
at least the ones I though were "public". Probably too many, but
possibly missed one.
* Steve Purcell's flymake-easy.el adaptor
(https://github.com/purcell/flymake-easy) seems to work, which is a
nice surprise. It hooks onto the legacy backend via the obsolete
aliases.
* Got rid of flymake-display-err-menu-for-current-line, since it wasn't
doing anything useful anyway.
The code is in the scratch/flymake-refactor branch on Savannah. There
are some 40 proper Changelog-style commits with profuse comments
explaining the changes. You can follow that story or review the final
patch, but keep M-x vc-region-history handy.
Here are a couple of screenshots taken from clean emacs -Q runs after
just M-x flymake-mode.
[-- Attachment #2: flymake-1.png --]
[-- Type: image/png, Size: 42732 bytes --]
[-- Attachment #3: flymake-2.png --]
[-- Type: image/png, Size: 43895 bytes --]
next reply other threads:[~2017-09-28 14:27 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 14:27 João Távora [this message]
2017-09-28 19:52 ` Flymake refactored Stefan Monnier
2017-09-29 0:22 ` João Távora
2017-09-29 3:11 ` Stefan Monnier
2017-10-01 16:52 ` João Távora
2017-10-01 20:50 ` Stefan Monnier
2017-10-02 1:01 ` João Távora
2017-10-02 3:12 ` Stefan Monnier
2017-10-03 0:33 ` João Távora
2017-10-03 1:09 ` Stefan Monnier
2017-09-29 12:51 ` Dmitry Gutov
2017-09-29 14:55 ` Ted Zlatanov
2017-09-29 15:03 ` Dmitry Gutov
2017-09-29 16:26 ` Ted Zlatanov
2017-09-29 17:35 ` Dmitry Gutov
2017-09-29 17:56 ` Ted Zlatanov
2017-09-30 15:07 ` Dmitry Gutov
2017-09-30 7:55 ` Marcin Borkowski
2017-09-30 23:43 ` João Távora
2017-10-01 8:53 ` Marcin Borkowski
2017-10-01 11:54 ` Mark Oteiza
2017-10-04 17:37 ` Simen Heggestøyl
2017-10-05 2:08 ` João Távora
2017-10-05 3:52 ` Mark Oteiza
2017-10-05 10:57 ` João Távora
2017-10-05 13:11 ` Stefan Monnier
2017-10-05 14:45 ` João Távora
2017-10-05 23:01 ` João Távora
2017-10-05 21:22 ` Mark Oteiza
2017-10-05 23:05 ` João Távora
2017-10-06 3:35 ` Stefan Monnier
2017-10-06 7:09 ` Lele Gaifax
2017-10-06 8:14 ` Eli Zaretskii
2017-10-06 8:19 ` Lele Gaifax
2017-10-06 9:48 ` Eli Zaretskii
2017-10-06 9:54 ` Lele Gaifax
2017-10-06 13:04 ` Mark Oteiza
2017-10-06 14:47 ` Lele Gaifax
2017-10-06 15:21 ` Mark Oteiza
2017-10-06 15:26 ` Mark Oteiza
2017-10-06 15:28 ` Lele Gaifax
2017-10-06 16:28 ` João Távora
2017-10-06 19:24 ` Lele Gaifax
2017-10-06 15:13 ` João Távora
2017-10-07 13:28 ` Stefan Monnier
2017-10-07 13:44 ` Eli Zaretskii
2017-10-07 14:40 ` Lele Gaifax
2017-10-07 14:52 ` Eli Zaretskii
2017-10-08 2:06 ` Stefan Monnier
2017-10-08 9:32 ` João Távora
2017-10-08 11:24 ` Lele Gaifax
2017-10-08 14:17 ` Stefan Monnier
2017-10-08 23:33 ` João Távora
2017-10-09 3:01 ` Stefan Monnier
2017-10-09 10:19 ` João Távora
2017-10-09 15:50 ` [SUSPECTED SPAM] " Stefan Monnier
2017-10-09 16:33 ` [PATCH] " Lele Gaifax
2017-10-07 6:31 ` Marcin Borkowski
2017-10-07 13:37 ` Stefan Monnier
2017-10-07 16:48 ` Marcin Borkowski
2017-10-06 12:54 ` John Wiegley
2017-10-06 15:17 ` Mark Oteiza
2017-10-06 16:04 ` João Távora
2017-10-06 21:22 ` Mark Oteiza
2017-10-06 22:03 ` João Távora
2017-10-07 13:31 ` Stefan Monnier
2017-10-07 16:02 ` João Távora
2017-10-07 16:07 ` João Távora
2017-10-07 18:18 ` Mark Oteiza
2017-10-08 9:06 ` João Távora
2017-10-08 12:51 ` Mark Oteiza
2017-10-08 23:21 ` João Távora
2017-10-10 14:27 ` Mark Oteiza
2017-10-10 15:20 ` João Távora
2017-10-10 16:10 ` Mark Oteiza
2017-10-05 11:28 ` Lele Gaifax
2017-10-05 15:12 ` Lele Gaifax
2017-10-10 10:40 ` Lele Gaifax
2017-10-10 12:27 ` 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=87h8vmj3tr.fsf@lolita \
--to=joaotavora@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--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 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).