diff options
author | Eli Zaretskii <eliz@gnu.org> | 2022-05-18 16:53:49 +0300 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2022-05-18 16:53:49 +0300 |
commit | b1620a44ff201966c9900a116a640597093e6030 (patch) | |
tree | 62f0ba6e71606226ecd355a9a068ff3be7b4dca1 /lisp/progmodes/flymake.el | |
parent | a67d8e0d70d5563044f9981795de9ee2876b6463 (diff) | |
download | emacs-b1620a44ff201966c9900a116a640597093e6030.tar.gz emacs-b1620a44ff201966c9900a116a640597093e6030.tar.bz2 emacs-b1620a44ff201966c9900a116a640597093e6030.zip |
; * lisp/progmodes/flymake.el (flymake-mode): Fix a typo.
Diffstat (limited to 'lisp/progmodes/flymake.el')
-rw-r--r-- | lisp/progmodes/flymake.el | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/progmodes/flymake.el b/lisp/progmodes/flymake.el index 46a4fdfa373..fbbfacfcfed 100644 --- a/lisp/progmodes/flymake.el +++ b/lisp/progmodes/flymake.el @@ -1104,7 +1104,7 @@ 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 +mechanisms that often), it can be useful to put something like the following in your init file: (setq next-error-function \\='flymake-goto-next-error) |