+2007-09-20 Eduard Wiebe <usenet@pusto.de> (tiny change)
+
+ * flymake.texi (Customizable variables): Face names don't end in -face.
+ Fix flymake-err-line-patterns template.
+ (Example -- Configuring a tool called directly): Fix init-function.
+ (Highlighting erroneous lines): Face names don't end in -face.
+
2007-09-05 Glenn Morris <rgm@gnu.org>
* custom.texi (Safe File Variables): Clarify `!' and risky variables.
@item flymake-err-line-patterns
Patterns for error/warning messages in the form @code{(regexp file-idx
-line-idx err-text-idx)}. @xref{Parsing the output}.
+line-idx col-idx err-text-idx)}. @xref{Parsing the output}.
@item flymake-compilation-prevents-syntax-check
A flag indicating whether compilation and syntax check of the same
A boolean flag indicating whether to start syntax check after a
newline character is added to the buffer.
-@item flymake-errline-face
+@item flymake-errline
A custom face for highlighting lines for which at least one error has
been reported.
-@item flymake-warnline-face
+@item flymake-warnline
A custom face for highlighting lines for which at least one warning
and no errors have been reported.
First, we write the @code{init-function}:
@lisp
-(defun flymake-perl-init (buffer)
+(defun flymake-perl-init ()
(let* ((temp-file (flymake-init-create-temp-buffer-copy
- buffer 'flymake-create-temp-inplace))
+ 'flymake-create-temp-inplace))
(local-file (concat (flymake-build-relative-filename
(file-name-directory
(buffer-file-name
Highlighting is implemented with overlays and happens in the process
sentinel, after calling the cleanup function. Two customizable faces
-are used: @code{flymake-errline-face} and
-@code{flymake-warnline-face}. Errors belonging outside the current
+are used: @code{flymake-errline} and
+@code{flymake-warnline}. Errors belonging outside the current
buffer are considered to belong to line 1 of the current buffer.
@node Interaction with other modes