292 |
@section Customizable variables |
@section Customizable variables |
293 |
@cindex Customizable variables |
@cindex Customizable variables |
294 |
|
|
295 |
This section summarises variables used for Flymake |
This section summarizes variables used for Flymake |
296 |
configuration. |
configuration. |
297 |
|
|
298 |
@table @code |
@table @code |
378 |
selected. If no match is found, @code{flymake-mode} is switched off. |
selected. If no match is found, @code{flymake-mode} is switched off. |
379 |
|
|
380 |
@item init-function |
@item init-function |
381 |
@code{init-function} is required to initialise the syntax check, |
@code{init-function} is required to initialize the syntax check, |
382 |
usually by creating a temporary copy of the buffer contents. The |
usually by creating a temporary copy of the buffer contents. The |
383 |
function must return @code{(list cmd-name arg-list)}. If |
function must return @code{(list cmd-name arg-list)}. If |
384 |
@code{init-function} returns null, syntax check is aborted, by |
@code{init-function} returns null, syntax check is aborted, by |
639 |
and the way it can be obtained can vary greatly for different projects. |
and the way it can be obtained can vary greatly for different projects. |
640 |
Therefore, a customizable variable |
Therefore, a customizable variable |
641 |
@code{flymake-get-project-include-dirs-function} is used to provide the |
@code{flymake-get-project-include-dirs-function} is used to provide the |
642 |
way to implement the desired behaviour. |
way to implement the desired behavior. |
643 |
|
|
644 |
The default implementation, @code{flymake-get-project-include-dirs-imp}, |
The default implementation, @code{flymake-get-project-include-dirs-imp}, |
645 |
uses a @code{make} call. This requires a correct base directory, that is, a |
uses a @code{make} call. This requires a correct base directory, that is, a |
658 |
Flymake can be configured to use different tools for performing syntax |
Flymake can be configured to use different tools for performing syntax |
659 |
checks. For example, it can use direct compiler call to syntax check a perl |
checks. For example, it can use direct compiler call to syntax check a perl |
660 |
script or a call to @code{make} for a more complicated case of a |
script or a call to @code{make} for a more complicated case of a |
661 |
@code{C/C++} source. The general idea is that simple files, like perl |
@code{C/C++} source. The general idea is that simple files, like perl |
662 |
scripts and html pages, can be checked by directly invoking a |
scripts and html pages, can be checked by directly invoking a |
663 |
corresponding tool. Files that are usually more complex and generally |
corresponding tool. Files that are usually more complex and generally |
664 |
used as part of larger projects, might require non-trivial options to |
used as part of larger projects, might require non-trivial options to |