summaryrefslogtreecommitdiff
path: root/lisp/progmodes/flymake.el
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2022-05-18 14:13:16 +0200
committerLars Ingebrigtsen <larsi@gnus.org>2022-05-18 15:33:57 +0200
commit960008aa982e0481c77ef6a8b871e9c4b3014491 (patch)
tree98146d5139e83662524cc3d1205f715e2dad6c04 /lisp/progmodes/flymake.el
parentd5540d7dbcee2a35dc928670ac210c5ffb909a75 (diff)
downloademacs-960008aa982e0481c77ef6a8b871e9c4b3014491.tar.gz
emacs-960008aa982e0481c77ef6a8b871e9c4b3014491.tar.bz2
emacs-960008aa982e0481c77ef6a8b871e9c4b3014491.zip
Mention next-error-function in flymake-mode doc string
* lisp/progmodes/flymake.el (flymake-mode): Note that you can set next-error-function (bug#32322).
Diffstat (limited to 'lisp/progmodes/flymake.el')
-rw-r--r--lisp/progmodes/flymake.el7
1 files changed, 7 insertions, 0 deletions
diff --git a/lisp/progmodes/flymake.el b/lisp/progmodes/flymake.el
index b5f4fff3c31..46a4fdfa373 100644
--- a/lisp/progmodes/flymake.el
+++ b/lisp/progmodes/flymake.el
@@ -1102,6 +1102,13 @@ The commands `flymake-goto-next-error' and
`flymake-goto-prev-error' can be used to navigate among Flymake
diagnostics annotated in the buffer.
+By default, `flymake-mode' doesn't override the \\[next-error] command, but
+if you're using Flymake a lot (and don't use the regular compilation
+mechanisms that often), if can be useful to put something like
+the following in your init file:
+
+ (setq next-error-function \\='flymake-goto-next-error)
+
The visual appearance of each type of diagnostic can be changed
by setting properties `flymake-overlay-control', `flymake-bitmap'
and `flymake-severity' on the symbols of diagnostic types (like