File: flycheck.html

package info (click to toggle)
flycheck 30-3
links: PTS, VCS
area: main
in suites: stretch
size: 4,172 kB
ctags: 1,544
sloc: lisp: 11,139; python: 733; makefile: 243; ruby: 23; cpp: 17; ada: 17; f90: 16; xml: 14; ansic: 12; haskell: 12; sh: 10; erlang: 10; php: 9; perl: 7; fortran: 3; sql: 1
file content (4130 lines) | stat: -rw-r--r-- 225,256 bytes
<!DOCTYPE html>
<html>
<!-- Modern on-the-fly syntax checking for GNU Emacs 24.

Copyright (C) 2014-2016 Sebastian Wiesner

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".

A copy of the license is also available from the Free Software
Foundation Web site at http://www.gnu.org/licenses/fdl.html.

Alternatively, you may copy, distribute and/or modify this documentation
under the terms of the Creative Commons Attribution-ShareAlike 4.0
International Public License. A copy of the license can be obtained at
https://creativecommons.org/licenses/by-sa/4.0/legalcode. -->
<!-- Created by GNU Texinfo 6.0, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Flycheck</title>

<meta name="description" content="Flycheck">
<meta name="keywords" content="Flycheck">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2any">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="#Top" rel="start" title="Top">
<link href="#Main-Index" rel="index" title="Main Index">
<link href="http://www.flycheck.org" rel="up" title="(dir)">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space: nowrap}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: serif; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>


</head>

<body lang="en">
<h1 class="settitle" align="center">Flycheck</h1>
















<a name="Top"></a>
<div class="header">
<p>
Next: <a href="#Introduction" accesskey="n" rel="next">Introduction</a>, Up: <a href="http://www.flycheck.org" accesskey="u" rel="up">(dir)</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Flycheck"></a>
<h1 class="top">Flycheck</h1>

<p>Modern on-the-fly syntax checking for GNU Emacs 24.
</p>
<p>Copyright &copy; 2014-2016 Sebastian Wiesner
</p>
<blockquote>
<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled &ldquo;GNU
Free Documentation License&rdquo;.
</p>
<p>A copy of the license is also available from the Free Software
Foundation Web site at <a href="http://www.gnu.org/licenses/fdl.html">http://www.gnu.org/licenses/fdl.html</a>.
</p>
<p>Alternatively, you may copy, distribute and/or modify this documentation
under the terms of the Creative Commons Attribution-ShareAlike 4.0
International Public License. A copy of the license can be obtained at
<a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a>.
</p></blockquote>


<p>Flycheck is a modern GNU Emacs package that provides on-the-fly syntax
checking for buffers.  It is intended as replacement for the older
Flymake package which is built into Emacs.
</p>
<p>See <a href="#Introduction">Introduction</a>, for more information about Flycheck.  For
installations instructions and a quick tutorial, see <a href="#Installation">Installation</a>
and <a href="#Quickstart">Quickstart</a> respectively.  See <a href="#Usage">Usage</a>, for a detailed user
guide.
</p>
<p><strong>With Flycheck installed you can read this manual inside Emacs
with <tt class="key">M-x flycheck-info</tt></strong>.  This opens Emacs&rsquo; built-in Info reader.
See <a href="http://www.gnu.org/software/texinfo/manual/info/info.html#Getting-Started">(info)Getting Started</a>, to see how to use this reader.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">&bull; <a href="#Introduction" accesskey="1">Introduction</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">An introduction to Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Installation" accesskey="2">Installation</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to install Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Quickstart" accesskey="3">Quickstart</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">A quick Flycheck tutorial
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Usage" accesskey="4">Usage</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to use Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Syntax-checker-definitions" accesskey="5">Syntax checker definitions</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to add new syntax checkers to Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Flycheck-hooks" accesskey="6">Flycheck hooks</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to hook into Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Flycheck-API" accesskey="7">Flycheck API</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">API documentation
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Supported-languages" accesskey="8">Supported languages</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">A list of supported languages
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Getting-Help" accesskey="9">Getting Help</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to obtain help about Flycheck
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#GNU-Free-Documentation-License">GNU Free Documentation License</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to copy this manual
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Main-Index">Main Index</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Index of Flycheck concepts
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Key-Index">Key Index</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Index of all keybindings
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Function-and-Variable-Index">Function and Variable Index</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Index of commands, options and types
</td></tr>
</table>

<hr>
<a name="Introduction"></a>
<div class="header">
<p>
Next: <a href="#Installation" accesskey="n" rel="next">Installation</a>, Previous: <a href="#Top" accesskey="p" rel="prev">Top</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Introduction-1"></a>
<h2 class="chapter">1 Introduction</h2>

<p>Flycheck provides modern on-the-fly syntax checking extension for GNU
Emacs 24, intended as replacement for the older Flymake extension which
is part of GNU Emacs.
</p>
<p>Flycheck runs various linting tools and services to automatically check
the contents of buffers while you are typing, and reports warnings and
errors directly in the buffer, in the mode line and in an optional error
list.  You can navigate errors and warnings in the current buffer, show
the corresponding messages, and copy errors to the kill ring.
</p>
<a name="index-features"></a>

<ul>
<li> Over 40 languages with more than 70 checkers.  See <a href="#Supported-languages">Supported languages</a>.
</li><li> Fully automatic, fail-safe, on-the-fly syntax checking in buffers
</li><li> In-buffer error highlighting, with fringe indicators
</li><li> Error navigation
</li><li> Auto-updating error list
</li><li> Many customisation options
</li><li> A comprehensive manual
</li><li> A simple API to add support for new languages and tools
</li><li> A “doesn&rsquo;t get in your way guarantee”
</li></ul>

<hr>
<a name="Installation"></a>
<div class="header">
<p>
Next: <a href="#Quickstart" accesskey="n" rel="next">Quickstart</a>, Previous: <a href="#Introduction" accesskey="p" rel="prev">Introduction</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Installation-1"></a>
<h2 class="chapter">2 Installation</h2>

<a name="Prerequisites"></a>
<h3 class="section">2.1 Prerequisites</h3>

<a name="index-prerequisites"></a>
<a name="index-operating-system"></a>

<p>Flycheck needs GNU Emacs 24.  Older releases of GNU Emacs or other
flavours of Emacs (e.g. XEmacs, Aquamacs, etc.) are <em>not</em>
supported.
</p>
<p>Flycheck works best on Unix-like operating systems.  It is extensively
tested on Linux and OS X.
</p>
<a name="index-Windows"></a>

<a name="windows_002dsupport"></a><p><b>Flycheck does not explicitly support
Windows</b>, but tries to maintain Windows compatibility and should
generally work fine on Windows, too.  However, we can neither answer
questions about Windows nor fix bugs that only occur on Windows without
the help of active Windows users.  Please watch out for
<a href="https://github.com/flycheck/flycheck/labels/B-Windows%20only">known Windows issues</a>!
</p>
<a name="Syntax-checking-tools"></a>
<h3 class="section">2.2 Syntax checking tools</h3>

<p>Flycheck does <em>not</em> check buffers itself.  It relies on
<em>external</em> programs to check buffers, which need to be installed
separately.  See <a href="#Supported-languages">Supported languages</a>, for a list of required programs
for each language supported by Flycheck.
</p>
<p>Most of these programs are available in the package repositories of
Linux distributions, or with the standard package managers of specific
programming languages (e.g. Rubygems, NPM, Cabal, etc.)
</p>
<a name="Installation-2"></a>
<h3 class="section">2.3 Installation</h3>

<a name="index-installation"></a>

<p>Install Flycheck via Emacs&rsquo; built-in package manager, from the
<a href="http://stable.melpa.org">MELPA Stable</a> repository:
</p>
<div class="example">
<pre class="example">M-x package-install RET flycheck
</pre></div>

<p>Alternatively, you may use the <a href="http://melpa.org">MELPA</a>
repository, which hosts the most recent development version.  Note that
these repositories are not included in GNU Emacs by default.
</p>
<p>You need to enable them explicitly, by adding the following to your init
file:
</p>
<div class="lisp">
<pre class="lisp">(require 'package)
(add-to-list 'package-archives
             '(&quot;melpa&quot; . &quot;http://melpa.org/packages/&quot;) t)
(package-initialize)
</pre></div>

<p>If you don&rsquo;t know where your init file is take a look at the value of
the variable <code>user-init-file</code> with <kbd>C-h v user-init-file</kbd>.
</p>
<hr>
<a name="Quickstart"></a>
<div class="header">
<p>
Next: <a href="#Usage" accesskey="n" rel="next">Usage</a>, Previous: <a href="#Installation" accesskey="p" rel="prev">Installation</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Quickstart-1"></a>
<h2 class="chapter">3 Quickstart</h2>
<a name="Install-and-enable-Flycheck"></a>
<h3 class="section">3.1 Install and enable Flycheck</h3>

<p>To get started with Flycheck, enable it by adding the following to your
init file:
</p>
<div class="lisp">
<pre class="lisp">(add-hook 'after-init-hook #'global-flycheck-mode)
</pre></div>

<p>If you don&rsquo;t know where your init file is take a look at the value of
the variable <code>user-init-file</code> with <kbd>C-h v user-init-file</kbd>.
</p>
<a name="Install-syntax-checker-tools"></a>
<h3 class="section">3.2 Install syntax checker tools</h3>

<p>Next you need to install syntax checking tools for the major modes you
are using.  For instance, for Python you may want to install
<a href="http://pylint.org">Pylint</a>:
</p>
<div class="example">
<pre class="example">$ pip install pylint
</pre></div>

<p>For Ruby, you might want to use <a href="https://github.com/bbatsov/rubocop">Rubocop</a> and
<a href="https://github.com/YorickPeterse/ruby-lint">ruby-lint</a>:
</p>
<div class="example">
<pre class="example">$ gem install rubocop ruby-lint
</pre></div>

<p>See <a href="#Supported-languages">Supported languages</a>, for a complete list of all languages that
Flycheck supports.
</p>
<a name="Check-syntax-in-a-buffer"></a>
<h3 class="section">3.3 Check syntax in a buffer</h3>

<p>Now switch to a Python or Ruby Mode buffer and run <kbd>M-x
flycheck-verify-setup</kbd> to check whether Flycheck is correctly setup.
</p>
<p>If everything is fine Flycheck will now check syntax using these tools,
when you visit a buffer in any of these languages.  Syntax checking
happens <em>automatically</em> when you save the buffer or make any
changes.  Flycheck highlights errors and warnings in the buffer,
indicates them in the fringe, and reports their numbers in the mode
line.
</p>
<p>You can also manually check a buffer with <kbd>C-c ! c</kbd>
(<code>flycheck-buffer</code>).
</p>
<a name="Navigate-and-list-errors"></a>
<h3 class="section">3.4 Navigate and list errors</h3>

<p>Use <kbd>C-c ! n</kbd> (<code>flycheck-next-error</code>) and <kbd>C-c ! p</kbd>
(<code>flycheck-previous-error</code>) to navigate between error locations.
If you keep the point at an error location, Flycheck will show the error
message in the echo area after a short delay.  You can also hover error
locations with the mouse and see the error message in a tooltip.
</p>
<p>To get an overview of all errors and warnings in the current buffer,
type <kbd>C-c ! l</kbd> (<code>flycheck-list-errors</code>) to pop up a list of all
errors in your current buffer.  The error list updates automatically
when you fix errors or introduce new ones, or when you switch to another
buffer.
</p>
<a name="More-features"></a>
<h3 class="section">3.5 More features</h3>

<p>All Flycheck commands are available in the Emacs menu at &lsquo;<samp>Syntax
checking</samp>&rsquo; in the &lsquo;<samp>Tools</samp>&rsquo; menu.
</p>
<img src="images/flycheck-menu.png" alt="images/flycheck-menu">

<p>The same menu is also available by clicking on the mode line lighter of
Flycheck.
</p>
<img src="images/flycheck-mode-line-menu.png" alt="images/flycheck-mode-line-menu">

<hr>
<a name="Usage"></a>
<div class="header">
<p>
Next: <a href="#Syntax-checker-definitions" accesskey="n" rel="next">Syntax checker definitions</a>, Previous: <a href="#Quickstart" accesskey="p" rel="prev">Quickstart</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Usage-1"></a>
<h2 class="chapter">4 Usage</h2>

<p>This chapter explains the usage of Flycheck in-depth.
</p>
<a name="index-flycheck_002dkeymap_002dprefix"></a>

<p><strong>Note:</strong> All commands in this chapter are documented with their
default key prefix <kbd>C-c !</kbd>.  You can customise this prefix with
<code>flycheck-keymap-prefix</code>, but remember your custom prefix while
reading this chapter.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">&bull; <a href="#Checking-buffers" accesskey="1">Checking buffers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How buffers are checked
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Syntax-checkers" accesskey="2">Syntax checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Tools used to check a buffer
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Reporting-results" accesskey="3">Reporting results</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How results of checks are reported
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Navigating-errors" accesskey="4">Navigating errors</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to navigate to Flycheck errors
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Displaying-errors" accesskey="5">Displaying errors</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to display error messages
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Killing-errors" accesskey="6">Killing errors</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to put error messages into the kill ring
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Listing-errors" accesskey="7">Listing errors</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to show a list of all errors
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Mode-line-display" accesskey="8">Mode line display</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to interpret Flycheck&rsquo;s mode line
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Configuring-checkers" accesskey="9">Configuring checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to configure syntax checkers
</td></tr>
</table>

<hr>
<a name="Checking-buffers"></a>
<div class="header">
<p>
Next: <a href="#Syntax-checkers" accesskey="n" rel="next">Syntax checkers</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Checking-buffers-1"></a>
<h3 class="section">4.1 Checking buffers</h3>

<a name="index-flycheck-mode"></a>
<a name="index-flycheck_002dmode"></a>
<a name="index-global_002dflycheck_002dmode"></a>
<a name="index-flycheck_002dglobal_002dmodes"></a>

<p>The minor mode <code>flycheck-mode</code> enables syntax checking in a single
buffer.  <code>global-flycheck-mode</code> automatically enables
<code>flycheck-mode</code> all buffers whenever possible.  You can exclude
specific major modes from <code>global-flycheck-mode</code> with
<code>flycheck-global-modes</code>.
</p>
<p><strong>Note:</strong> <code>global-flycheck-mode</code> does not enable
<code>flycheck-mode</code> for remote or encrypted files.  The former is flaky
and might be very slow, and the latter would leak confidential data to
temporary directories.  You may still check syntax in these buffers by
manually enabling <code>flycheck-mode</code> with <kbd>M-x flycheck-mode</kbd>.
However, this is <em>not</em> recommended for said reasons.
</p>
<p>Add the following code to your init file to enable syntax checking
permanently:
</p>
<div class="lisp">
<pre class="lisp">(add-hook 'after-init-hook #'global-flycheck-mode)
</pre></div>

<p>When <code>flycheck-mode</code> is enabled, Flycheck automatically checks a
buffer whenever
</p>
<ul>
<li> the buffer is saved,
</li><li> new lines are inserted,
</li><li> or a short time after you stopped to make changes to the buffer.
</li></ul>

<p>You can customise this behaviour by changing
<code>flycheck-check-syntax-automatically</code>:
</p>
<dl>
<dt><a name="index-flycheck_002dcheck_002dsyntax_002dautomatically"></a>User Option: <strong>flycheck-check-syntax-automatically</strong></dt>
<dd><p>A list of events that trigger a new syntax check in the current buffer:
</p>
<dl compact="compact">
<dt><code>save</code></dt>
<dd><p>Check the buffer immediately after it was saved.
</p></dd>
<dt><code>idle-change</code></dt>
<dd><a name="index-flycheck_002didle_002dchange_002ddelay"></a>
<p>Check the buffer a short time after the last change to the buffer.  The
delay is customisable with <code>flycheck-idle-change-delay</code>.
</p></dd>
<dt><code>new-line</code></dt>
<dd><p>Check the buffer immediately after a new line was inserted.
</p></dd>
<dt><code>mode-enabled</code></dt>
<dd><p>Check the buffer immediately after Flycheck Mode was enabled.
</p></dd>
</dl>

<p>For instance, with the following code in your init file Flycheck will
only check the buffer when it is saved, but never while you are making
changes to the buffer:
</p>
<div class="example">
<pre class="example">(setq flycheck-check-syntax-automatically '(mode-enabled save))
</pre></div>
</dd></dl>

<p>In addition to automatic syntax checking you can always check the
current buffer manually:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-c"></a>
<a name="index-flycheck_002dbuffer"></a>
</dd>
<dt><kbd>C-c ! c</kbd></dt>
<dt><kbd>M-x flycheck-buffer</kbd></dt>
<dd><p>Check syntax in the current buffer.
</p></dd>
</dl>

<p><strong>Note:</strong> If syntax checking does not work, please check your
setup:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-v"></a>
<a name="index-flycheck_002dverify_002dsetup"></a>
</dd>
<dt><kbd>C-c ! v</kbd></dt>
<dt><kbd>M-x flycheck-verify-setup</kbd></dt>
<dd><p>Popup a buffer with information about the Flycheck setup for the current
buffer.
</p>
<p>Lists the syntax checkers available for the current buffer, together
with potential problems in their setup.
</p></dd>
</dl>

<a name="index-flycheck_002dtemp_002dprefix"></a>

<p>During syntax checks Flycheck creates temporary files to feed to
contents of the current buffer to external programs.  You can change the
prefix used for the names of these temporary files with
<code>flycheck-temp-prefix</code>.
</p>
<hr>
<a name="Syntax-checkers"></a>
<div class="header">
<p>
Next: <a href="#Reporting-results" accesskey="n" rel="next">Reporting results</a>, Previous: <a href="#Checking-buffers" accesskey="p" rel="prev">Checking buffers</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Syntax-checkers-1"></a>
<h3 class="section">4.2 Syntax checkers</h3>

<a name="index-syntax-checker"></a>
<a name="index-syntax-checker-selection_002c-automatic"></a>
<a name="index-automatic-syntax-checker-selection"></a>

<p>Flycheck does not check buffers by itself, but relies on external
<em>syntax checkers</em>.  When checking a buffer Flycheck automatically
selects the best syntax checker from <code>flycheck-checkers</code>:
</p>
<dl>
<dt><a name="index-flycheck_002dcheckers"></a>User Option: <strong>flycheck-checkers</strong></dt>
<dd><p>A list of all syntax checkers available for syntax checking.
</p>
<p>A syntax checker in this list is a <em>registered</em> syntax checker.
</p></dd></dl>

<a name="index-chaining-of-syntax-checkers"></a>

<p>Flycheck may apply further syntax checkers to the current buffer, if the
selected syntax checker <em>chains</em> to other syntax checkers.  For
instance, the <code>emacs-lisp</code> syntax checker, which checks Emacs Lisp
with Emacs&rsquo; byte compiler, <em>chains</em> to the
<code>emacs-lisp-checkdoc</code> syntax checker, which checks Emacs Lisp for
violations of documentation conventions, <a href="http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Documentation-Tips">(elisp)Documentation
Tips</a>.  In Emacs Lisp buffers, Flycheck will first use
<code>emacs-lisp</code>, and then <code>emacs-lisp-checkdoc</code>.
</p>
<p>Flycheck ignores chained checkers which are not contained in
<code>flycheck-checkers</code>.
</p>
<p>Like everything else in GNU Emacs, syntax checkers have online
documentation as well.  If you are interested what major modes a
particular syntax checker in <code>flycheck-checkers</code> supports, or what
tool it uses, type <tt class="key">C-c ! ?</tt>:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-_003f"></a>
<a name="index-flycheck_002ddescribe_002dchecker"></a>
</dd>
<dt><kbd>C-c ! ?</kbd></dt>
<dt><kbd>M-x flycheck-describe-checker</kbd></dt>
<dd><p>Prompt for a syntax checker and show its documentation.
</p>
<p>The documentation includes the name of the program or service used by
the syntax checker, a list of major modes in which the checker will be
used, and a list of its options.
</p></dd>
</dl>

<a name="index-syntax-checker-selection_002c-manual"></a>
<a name="index-manual-syntax-checker-selection"></a>

<p>Instead of letting Flycheck select a syntax checker automatically you
can also explicitly tell Flycheck which checker to use for the current
buffer, by manually selecting a specific syntax checker:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-s"></a>
<a name="index-flycheck_002dselect_002dchecker"></a>
</dd>
<dt><kbd>C-c ! s</kbd></dt>
<dt><kbd>M-x flycheck-select-checker</kbd></dt>
<dd><p>Prompt for a syntax checker and select this syntax checker for the
current buffer.
</p>
<a name="index-C_002du-C_002dc-_0021-s"></a>
</dd>
<dt><kbd>C-u C-c ! s</kbd></dt>
<dt><kbd>C-u M-x flycheck-select-checker</kbd> Remove any manual</dt>
<dd><p>syntax checker selection for the current buffer, and let Flycheck
automatically select a syntax checker from <code>flycheck-checkers</code>
again.
</p></dd>
</dl>

<p>You can also select a syntax checker via the variable
<code>flycheck-checker</code>.  In fact, <code>flycheck-select-checker</code>
just sets this variable accordingly:
</p>
<dl>
<dt><a name="index-flycheck_002dchecker"></a>Variable: <strong>flycheck-checker</strong></dt>
<dd><p>A syntax checker to use for the current buffer.
</p>
<p>If nil (the default), Flycheck will automatically select the best
checker from <code>flycheck-checkers</code>.
</p>
<p>If set to a syntax checker, Flycheck will use this syntax checker for
the current buffer, and never automatically select any other.  Flycheck
still runs chained checkers, though.
</p>
<p>If the syntax checker selected by this variable does not work in the
current buffer, Flycheck signals an error.
</p>
<p>You can set this variable locally.  For instance, if your Python project
mandates <a href="http://flake8.readthedocs.org/en/2.2.3/">Flake8</a> as a
syntax checker, you can tell Flycheck to only use the corresponding
checker <code>python-flake8</code> in Python files of your project by setting
<code>flycheck-checker</code> as a directory-local variable in the top-level
directory of your project with <kbd>M-x add-dir-local-variable RET
python-mode RET flycheck-checker RET python-flake8</kbd>.  See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Directory-Variables">(emacs)Directory
Variables</a>, for more information about directory variables.
</p></dd></dl>

<p>Occasionally you may want to disable specific syntax checkers
completely, so that they can never be used at all, neither via automatic
nor via manual selection:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-x"></a>
<a name="index-flycheck_002ddisable_002dchecker"></a>
</dd>
<dt><kbd>C-c ! x</kbd></dt>
<dt><kbd>M-x flycheck-disable-checker</kbd></dt>
<dd><p>Prompt for a syntax checker to disable in the current buffer.
</p>
<a name="index-C_002du-C_002dc-_0021-x"></a>
</dd>
<dt><kbd>C-u C-c ! x</kbd></dt>
<dt><kbd>C-u M-x flycheck-disable-checker</kbd></dt>
<dd><p>Prompt for a syntax checker to re-enable in the current buffer.
</p></dd>
</dl>

<p>This is particularly useful if you want to disable syntax checkers that
are chained after others.  For instance, if you do not care for
documentation conventions of Emacs Lisp you may not need for the
<code>emacs-lisp-checkdoc</code> checker, so you can disable it for the
current buffer with <tt class="key">M-x flycheck-disable-checker RET
emacs-lisp-checkdoc</tt>.
</p>
<p><code>flycheck-disable-checker</code> actually sets the buffer-local value of
the <code>flycheck-disabled-checkers</code> option:
</p>
<dl>
<dt><a name="index-flycheck_002ddisabled_002dcheckers"></a>User Option: <strong>flycheck-disabled-checkers</strong></dt>
<dd><p>A list of disabled syntax checkers.  Flycheck will <em>never</em> use
disabled syntax checkers to check a buffer.
</p>
<p>You can customise this variable with <tt class="key">M-x customize-variable RET
flycheck-disabled-checkers</tt> or set its default value in your init file
to permanently disable specific checkers.  For instance, to permanently
disable Clang for all C/C++ buffers:
</p>
<div class="lisp">
<pre class="lisp">(setq-default flycheck-disabled-checkers '(c/c++-clang))
</pre></div>

<p>You can also disable checkers via local variables.  For instance, to
disable <code>emacs-lisp-checkdoc</code> for your entire project, add it to
<code>flycheck-disabled-checkers</code> in the <samp>.dir-locals.el</samp> file of
your project:
</p>
<div class="lisp">
<pre class="lisp">((emacs-lisp-mode (flycheck-disabled-checkers emacs-lisp-checkdoc)))
</pre></div>

<p>See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Directory-Variables">(emacs)Directory Variables</a>, for more information about directory
variables.
</p></dd></dl>

<hr>
<a name="Reporting-results"></a>
<div class="header">
<p>
Next: <a href="#Navigating-errors" accesskey="n" rel="next">Navigating errors</a>, Previous: <a href="#Syntax-checkers" accesskey="p" rel="prev">Syntax checkers</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Reporting-results-of-syntax-checking"></a>
<h3 class="section">4.3 Reporting results of syntax checking</h3>

<p>When a syntax check in the current buffer has finished, Flycheck reports
the results of the syntax checkers used by the check in the current
buffer:
</p>
<ul>
<li> It highlights errors and warnings reported by a syntax checking in the
buffer according to <code>flycheck-highlighting-mode</code>,
</li><li> and indicates these locations in the fringe according to
<code>flycheck-indication-mode</code>.
</li></ul>

<dl>
<dt><a name="index-flycheck_002dhighlighting_002dmode"></a>User Option: <strong>flycheck-highlighting-mode</strong></dt>
<dd><p>How Flycheck highlights errors and warnings in the buffer:
</p>
<dl compact="compact">
<dt><code>lines</code></dt>
<dd><p>Highlight the whole line, ignoring any column information.
</p></dd>
<dt><code>columns</code></dt>
<dd><p>Highlight the column of the error, if the error has a column, otherwise
behave as <code>lines</code>.
</p></dd>
<dt><code>symbols</code></dt>
<dd><p>Highlight the symbol at the error column, if any, otherwise behave like
<code>columns</code>.  This is default
</p></dd>
<dt><code>sexps</code></dt>
<dd><p>Highlight the expression at the error column, if any, otherwise behave
like <code>columns</code>.  <strong>Warning:</strong> <code>sexps</code> can be <em>very</em>
slow in some major modes, notably the built-in <code>python-mode</code>.
</p></dd>
<dt><code>nil</code></dt>
<dd><p>Do not highlight errors at all.
</p></dd>
</dl>

<a name="index-flycheck_002derror"></a>
<a name="index-flycheck_002dwarning"></a>
<a name="index-flycheck_002dinfo"></a>

<p>Flycheck uses the <code>flycheck-error</code>, <code>flycheck-warning</code> and
<code>flycheck-info</code> faces to highlight errors, warnings and info
messages respectively.
</p></dd></dl>

<dl>
<dt><a name="index-flycheck_002dindication_002dmode"></a>User Option: <strong>flycheck-indication-mode</strong></dt>
<dd><p>How Flycheck indicates errors and warnings:
</p>
<dl compact="compact">
<dt><code>left-fringe</code></dt>
<dt><code>right-fringe</code></dt>
<dd><p>Indicate errors in the left or right fringe respectively.
See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Fringes">(emacs)Fringes</a>, for more information about fringes.
</p>
<p>Flycheck uses the <code>flycheck-fringe-error</code>,
<code>flycheck-fringe-warning</code>, and <code>flycheck-fringe-info</code> faces
for the indicators for the corresponding error levels.
</p></dd>
<dt><code>nil</code></dt>
<dd><p>Do not indicate errors and warnings.
</p></dd>
</dl>
</dd></dl>

<a name="index-flycheck_002dchecker_002derror_002dthreshold"></a>

<p>To avoid flooding a buffer with excessive reports, Flycheck discards any
reports and <em>disables</em> the corresponding syntax checker
subsequently, if the total number of reported errors of any level
exceeds the value of <code>flycheck-checker-error-threshold</code>.
</p>
<a name="index-flycheck_002dclear"></a>

<p>You can explicitly clear with the <code>flycheck-clear</code> command.
</p>
<hr>
<a name="Navigating-errors"></a>
<div class="header">
<p>
Next: <a href="#Displaying-errors" accesskey="n" rel="next">Displaying errors</a>, Previous: <a href="#Reporting-results" accesskey="p" rel="prev">Reporting results</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Navigating-errors-1"></a>
<h3 class="section">4.4 Navigating errors</h3>

<a name="index-flycheck_002dstandard_002derror_002dnavigation"></a>

<p>By default, Flycheck integrates into standard error navigation commands
of Emacs: <kbd>M-g n</kbd> (<code>next-error</code>) and <kbd>M-g p</kbd>
(<code>previous-error</code>) will navigate between Flycheck warnings and
errors in the current buffer.  See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Compilation-Mode">(emacs)Compilation Mode</a>, for more
information about these commands.  You can disable this integration by
setting <code>flycheck-standard-error-navigation</code> to nil, and
re-enabling <code>flycheck-mode</code> afterwards.
</p>
<p><strong>Note:</strong> With standard error navigation <em>visible</em> compilation
buffers (e.g. from M-x compile, M-x grep, M-x occur, etc.)  take
precedence over Flycheck errors.
</p>
<p>Flycheck provides an independent set of navigation commands which will
always navigate Flycheck errors in the current buffer, regardless of
visible compilation buffers and
<code>flycheck-standard-error-navigation</code>:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-n"></a>
<a name="index-flycheck_002dnext_002derror"></a>
</dd>
<dt><kbd>C-c ! n</kbd></dt>
<dt><kbd>M-x flycheck-next-error</kbd></dt>
<dd><p>Jump to the next error.
</p>
<p>With prefix argument, jump forwards by as many errors as specified by
the prefix argument, e.g. <kbd>M-3 C-c ! n</kbd> will move to the 3rd error
from the current point.  With negative prefix argument, move to previous
errors instead.  Signal an error, if there are no more Flycheck errors.
</p>
<a name="index-C_002dc-_0021-p"></a>
<a name="index-flycheck_002dprevious_002derror"></a>
</dd>
<dt><kbd>C-c ! p</kbd></dt>
<dt><kbd>M-x flycheck-previous-error</kbd></dt>
<dd><p>Jump to the previous Flycheck error.
</p>
<p>With prefix argument, jump backwards by as many errors as specified by
the prefix argument, e.g. <kbd>M-3 C-c ! p</kbd> will move to the 3rd error
before the current point.  With negative prefix argument, move to next
errors instead.  Signal an error, if there are no more Flycheck errors.
</p>
<a name="index-flycheck_002dfirst_002derror"></a>
</dd>
<dt><kbd>M-x flycheck-first-error</kbd></dt>
<dd><p>Jump to the first Flycheck error.
</p>
<p>With prefix argument, jump forwards to by as many errors as specified by
the prefix argument, e.g. <kbd>M-3 M-x flycheck-first-error</kbd> moves to
the 3rd error from the beginning of the buffer.  With negative prefix
argument, move to the last error instead.
</p></dd>
</dl>

<p>By default, these commands consider all errors in the current buffer.
With <code>flycheck-navigation-minimum-level</code> you can restrict them to
errors above certain levels:
</p>
<dl>
<dt><a name="index-flycheck_002dnavigation_002dminimum_002dlevel"></a>User Option: <strong>flycheck-navigation-minimum-level</strong></dt>
<dd><p>The minimum levels of errors to consider for navigation.
</p>
<p>If set to an error level, only navigate to errors whose level is as
least as severe as this one.  If nil, navigate to all errors.
</p></dd></dl>

<hr>
<a name="Displaying-errors"></a>
<div class="header">
<p>
Next: <a href="#Killing-errors" accesskey="n" rel="next">Killing errors</a>, Previous: <a href="#Navigating-errors" accesskey="p" rel="prev">Navigating errors</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Displaying-errors-1"></a>
<h3 class="section">4.5 Displaying errors</h3>

<p>When the point moves to an error location Flycheck automatically
displays the error at point after a short delay:
</p>
<dl>
<dt><a name="index-flycheck_002ddisplay_002derrors_002ddelay"></a>User Option: <strong>flycheck-display-errors-delay</strong></dt>
<dd><p>The number of seconds to wait before displaying the error at point.
Floating point numbers can express fractions of seconds.
</p></dd></dl>

<p>You can also display errors at point explicitly with <kbd>C-c ! h</kbd>:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-h"></a>
<a name="index-flycheck_002ddisplay_002derror_002dat_002dpoint"></a>
</dd>
<dt><kbd>C-c ! h</kbd></dt>
<dt><kbd>M-x flycheck-display-error-at-point</kbd></dt>
<dd><p>Show the error(s) at point.
</p></dd>
</dl>

<p>By default Flycheck shows the error message and the error ID in the echo
area, but you can customise how Flycheck displays errors with
<code>flycheck-display-errors-function</code>:
</p>
<dl>
<dt><a name="index-flycheck_002ddisplay_002derrors_002dfunction"></a>User Option: <strong>flycheck-display-errors-function</strong></dt>
<dd><p>A function to display errors.  The function is called with a list of
Flycheck error objects to display.  See <a href="#Errors">Errors</a>, for more information
about these objects.
</p></dd></dl>

<a name="index-error-display-function"></a>
<a name="index-functions-for-error-display"></a>
<p>Flycheck provides some built-in display functions:
</p>
<dl>
<dt><a name="index-flycheck_002ddisplay_002derror_002dmessages"></a>Function: <strong>flycheck-display-error-messages</strong></dt>
<dd><p>Show error messages and IDs in the echo area.
</p></dd></dl>

<dl>
<dt><a name="index-flycheck_002ddisplay_002derror_002dmessages_002dunless_002derror_002dlist"></a>Function: <strong>flycheck-display-error-messages-unless-error-list</strong></dt>
<dd><p>Like <code>flycheck-display-error-messages</code>, but does not show anything
if the error list is visible.  See <a href="#Listing-errors">Listing errors</a>, for more
information about the error list.
</p></dd></dl>

<p>Alternatively the <a href="https://github.com/flycheck/flycheck-pos-tip">flycheck-pos-tip</a>
extension provides an display function which shows error messages in a
graphical popup.
</p>
<a name="index-error-tooltip"></a>
<a name="index-display_002dlocal_002dhelp"></a>
<a name="index-C_002dh-_002e"></a>
<p>In addition to this display mechanism, Flycheck adds a tooltip to each
error which appears when you hover the error location with the mouse
pointer.  You can force Emacs to show the contents of the tooltip in the
echo area with <kbd>C-h .</kbd> (<code>display-local-help</code>).
</p>
<p>The contents of this tooltip are created with
<code>flycheck-help-echo-function</code>:
</p>
<dl>
<dt><a name="index-flycheck_002dhelp_002decho_002dfunction"></a>User Option: <strong>flycheck-help-echo-function</strong></dt>
<dd><p>A function to compute the contents of the error tooltips.
</p>
<p>By default Flycheck adds the error message and the error ID of all
errors at point to the tooltip contents.
</p></dd></dl>

<hr>
<a name="Killing-errors"></a>
<div class="header">
<p>
Next: <a href="#Listing-errors" accesskey="n" rel="next">Listing errors</a>, Previous: <a href="#Displaying-errors" accesskey="p" rel="prev">Displaying errors</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Killing-errors-1"></a>
<h3 class="section">4.6 Killing errors</h3>

<p>You can also put error messages into the kill ring:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-C_002dw"></a>
<a name="index-flycheck_002dcopy_002derrors_002das_002dkill"></a>
</dd>
<dt><kbd>C-c ! C-w</kbd></dt>
<dt><kbd>M-x flycheck-copy-errors-as-kill</kbd></dt>
<dd><p>Copy all Flycheck error messages at point into the kill ring.
</p>
<p>Each error message is killed <em>separately</em>, so <kbd>C-y</kbd>
(<code>yank</code>) only yanks a single error message.  You can use <kbd>M-y</kbd>
(<code>yank-pop</code>) to cycle between the killed messages after yanking the
first one.
</p>
<a name="index-C_002du-C_002dc-_0021-C_002dw"></a>
</dd>
<dt><kbd>C-u C-c ! C-w</kbd></dt>
<dt><kbd>C-u M-x flycheck-copy-errors-as-kill</kbd></dt>
<dd><p>Copy all Flycheck error messages at point, including their IDs.
</p>
<a name="index-M_002d0-C_002dc-_0021-C_002dw"></a>
</dd>
<dt><kbd>M-0 C-c ! C-w</kbd></dt>
<dt><kbd>M-0 M-x flycheck-copy-errors-as-kill</kbd></dt>
<dd><p>Copy the IDs of the errors at point.
</p></dd>
</dl>

<hr>
<a name="Listing-errors"></a>
<div class="header">
<p>
Next: <a href="#Mode-line-display" accesskey="n" rel="next">Mode line display</a>, Previous: <a href="#Killing-errors" accesskey="p" rel="prev">Killing errors</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Listing-errors-1"></a>
<h3 class="section">4.7 Listing errors</h3>

<p>To get an overview of all errors in the current buffer you can popup an
error list:
</p>
<dl compact="compact">
<dd><a name="index-list_002dflycheck_002derrors"></a>
<a name="index-C_002dc-_0021-l"></a>
<a name="index-flycheck_002dlist_002derrors"></a>
</dd>
<dt><kbd>C-c ! l</kbd></dt>
<dt><kbd>M-x flycheck-list-errors</kbd></dt>
<dt><kbd>M-x list-flycheck-errors</kbd></dt>
<dd><p>List all errors in the current buffer.
</p>
<a name="index-flycheck_002derror_002dlist_002dafter_002drefresh_002dhook"></a>

<p>The error list automatically refreshes itself after a syntax check.  It
also follows the current buffer and window, and automatically updates to
show the errors of the new buffer if you switch to another buffer or
window.  After each refresh the hook
<code>flycheck-error-list-after-refresh-hook</code>.
</p></dd>
</dl>

<p>In the error list window the following keybindings are available:
</p>
<dl compact="compact">
<dt><kbd>n</kbd></dt>
<dd><p>Move to the next error.
</p></dd>
<dt><kbd>p</kbd></dt>
<dd><p>Move to the previous error.
</p></dd>
<dt><kbd>f</kbd></dt>
<dd><p>Filter the list, showing only errors whose level is above a threshold of
your choice.
</p></dd>
<dt><kbd>F</kbd></dt>
<dd><p>Remove all filters.
</p></dd>
<dt><kbd>q</kbd></dt>
<dd><p>Hide the error list window.
</p></dd>
<dt><kbd>RET</kbd></dt>
<dd><p>Jump to the location of the error at point.
</p></dd>
<dt><kbd>g</kbd></dt>
<dd><p>Refresh the error list, by triggering a new syntax check in the
associated buffer.
</p></dd>
<dt><kbd>S</kbd></dt>
<dd><p>Sort the error list by the column at point.  Press repeatedly to inverse
the sorting order.
</p>
<p>For instance, you can sort errors by their level by moving the point
onto the text of the &lsquo;<samp>Level</samp>&rsquo; column, and then pressing <kbd>S</kbd>.
You can achieve the same effect by clicking on the column header.
</p></dd>
</dl>

<p>By default, the error list shows all errors in the current buffer.  In
addition to filtering manually, you can restrict it to errors
above certain levels with <code>flycheck-error-list-minimum-level</code>:
</p>
<dl>
<dt><a name="index-flycheck_002derror_002dlist_002dminimum_002dlevel"></a>User Option: <strong>flycheck-error-list-minimum-level</strong></dt>
<dd><p>The minimum level of errors to display in the error list.
</p>
<p>If set to an error level, only displays errors whose error level
is at least as severe as this one in the error list.  If nil,
display all errors.
</p></dd></dl>

<a name="index-flycheck_002derror_002dlist_002dhighlight"></a>

<p>When you move the point in the current buffer while the error list is
visible, all errors on the current line are highlighted in the error
list with the <code>flycheck-error-list-highlight</code> face.
</p>
<hr>
<a name="Mode-line-display"></a>
<div class="header">
<p>
Next: <a href="#Configuring-checkers" accesskey="n" rel="next">Configuring checkers</a>, Previous: <a href="#Listing-errors" accesskey="p" rel="prev">Listing errors</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Mode-line-display-1"></a>
<h3 class="section">4.8 Mode line display</h3>

<p>Flycheck always indicates its current state in the mode line, with one
of the following strings:
</p>
<dl compact="compact">
<dt>&lsquo;<samp>FlyC</samp>&rsquo;</dt>
<dd><p>There are no errors in the current buffer.
</p></dd>
<dt>&lsquo;<samp>FlyC*</samp>&rsquo;</dt>
<dd><p>Flycheck currently checks the current buffer.
</p></dd>
<dt>&lsquo;<samp>FlyC:3/5</samp>&rsquo;</dt>
<dd><p>There are three errors and five warnings in the current buffer.
</p></dd>
<dt>&lsquo;<samp>FlyC-</samp>&rsquo;</dt>
<dd><p>Flycheck did not find any syntax checker for the current buffer.  Try
<kbd>C-c ! v</kbd> (<code>flycheck-verify-setup</code>) to find out why.
</p></dd>
<dt>&lsquo;<samp>FlyC!</samp>&rsquo;</dt>
<dd><p>The syntax check failed.  Inspect the &lsquo;<samp>*Messages*</samp>&rsquo; buffer for more
information about the failure.
</p></dd>
<dt>&lsquo;<samp>FlyC?</samp>&rsquo;</dt>
<dd><p>The syntax check had a dubious result.  The definition of the syntax
checker may be flawed.  Inspect the &lsquo;<samp>*Messages*</samp>&rsquo; buffer for
details.
</p></dd>
</dl>

<p>This indicator should <strong>never</strong> appear for built-in syntax
checkers.  If it does, please consider reporting an issue to the
Flycheck developers.  See <a href="#Issues">Issues</a>, for more information.
</p>
<p>The 3rd party extension
<a href="https://github.com/flycheck/flycheck-color-mode-line">flycheck-color-mode-line</a>
automatically changes the background colour of the mode line according
to the results of the last syntax check.
</p>
<hr>
<a name="Configuring-checkers"></a>
<div class="header">
<p>
Previous: <a href="#Mode-line-display" accesskey="p" rel="prev">Mode line display</a>, Up: <a href="#Usage" accesskey="u" rel="up">Usage</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Configuring-syntax-checkers"></a>
<h3 class="section">4.9 Configuring syntax checkers</h3>

<p>Flycheck provides a rich interface to configure syntax checkers.  There
are three different kinds of options for syntax checkers:
</p>
<ul>
<li> <em>Syntax checker options</em> which directly change specific settings of
syntax checkers,
</li><li> <em>syntax checker configuration files</em> which point syntax checkers to
configuration files which can comprehensively configure a syntax
checker, and
</li><li> <em>syntax checker executables</em> which change the executables that
Flycheck runs for syntax checkers.
</li></ul>

<a name="Syntax-checker-options-1"></a>
<h4 class="subsection">4.9.1 Syntax checker options</h4>

<a name="Syntax-checker-options"></a><a name="index-syntax-checker-options"></a>
<a name="index-options-of-syntax-checkers"></a>

<p>Man syntax checkers can be configured via individual options.  For
instance, the <code>flycheck-flake8-maximum-line-length</code> tells the
<code>python-flake8</code> syntax checker about the maximum number of
characters allowed on a line.  Use the command
<code>flycheck-describe-checker</code> to see what options a syntax checker
provides.  Type <kbd>M-x customize-group RET flycheck-options</kbd> to get a
list of all available options.
</p>
<p>Options are mainly intended to be set per file or per project via file
or directory variables.  See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#File-Variables">(emacs)File Variables</a>, and
<a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Directory-Variables">(emacs)Directory Variables</a> respectively, for more information.
</p>
<p>For instance, if you the following file variables section at the end of
a Python file, the <code>python-flake8</code> syntax checker will warn about
lines longer than 100 characters, rather than the default limit of 80
characters:
</p>
<div class="example">
<pre class="example"># Local Variables:
# flycheck-flake8-maximum-line-length: 100
# End:
</pre></div>

<a name="Syntax-checker-configuration-files-1"></a>
<h4 class="subsection">4.9.2 Syntax checker configuration files</h4>

<a name="Syntax-checker-configuration-files"></a><a name="index-syntax-checker-configuration-files"></a>
<a name="index-configuration-files-of-syntax-checkers"></a>

<p>Some syntax checkers also read configuration files.  These syntax
checkers have an associated <em>configuration file variable</em> which
specifies the path to the configuration file.  All configuration file
variables are customisable via <kbd>M-x customize-group RET
flycheck-config-files</kbd>.
</p>
<p>If the value of a configuration file variable is nil, Flycheck will not
use any configuration file for the corresponding syntax checker.  If it
is a string, however, Flycheck tries to locate an appropriate
configuration file, with the following procedure:
</p>
<ol>
<li> If the value contains a directory separator, expand the path against the
<code>default-directory</code> of the current buffer.
</li><li> If the buffer has a file name, search the buffer&rsquo;s directory and any
ancestor directories up to the root directory for the configuration
file.
</li><li> Eventually try to find the configuration file in the user&rsquo;s home
directory.
</li></ol>

<p>If any of these steps returns an existing file, this file is given to
the syntax checker.  For instance, assume you edit the file
<samp>foo/bar/hello.py</samp> in the following project layout:
</p>
<div class="example">
<pre class="example">.
├── .pylintrc
├── README.rst
├── foo
│   ├── __init__.py
│   └── bar
│       ├── __init__.py
│       └── hello.py
└── setup.py
</pre></div>

<p>When using the <code>python-pylint</code> syntax checker, Flycheck would find
the file <samp>.pylintrc</samp> and pass it to <code>pylint</code>.  This file
could then contain project-wide style settings for your Python code.
</p>
<p>You can change the default procedure for locating configuration files by
adding or replacing functions in
<code>flycheck-locate-config-file-functions</code>:
</p>
<dl>
<dt><a name="index-flycheck_002dlocate_002dconfig_002dfile_002dfunctions"></a>User Option: <strong>flycheck-locate-config-file-functions</strong></dt>
<dd><p>Functions to locate configuration files.
</p>
<p>Each function accepts two arguments <var>value</var> and <var>checker</var>.
<var>value</var> is the value of the configuration file variable, and
<var>checker</var> is the syntax checker to locate a configuration file for.
The function shall either return a string with the absolute path to an
existing configuration file, or nil if it could not locate the file.
</p>
<p>Flycheck calls the functions in order of appearance, until the first
function returns nil.  If all functions return nil, no configuration
file is given to the syntax checker.
</p></dd></dl>

<p><strong>Note:</strong> The formats of configuration files are specific to each
syntax checker.  Please consult the documentation of the corresponding
checker tool for information about the configuration file format
understood by the tool.
</p>
<p>Like syntax checker options (see <a href="#Syntax-checker-options">Syntax checker options</a>) you can
set these variables with file or directory variables.  See <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#File-Variables">(emacs)File
Variables</a>, and <a href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Directory-Variables">(emacs)Directory Variables</a> respectively,
for more information.
</p>
<a name="Syntax-checker-executables-1"></a>
<h4 class="subsection">4.9.3 Syntax checker executables</h4>

<a name="Syntax-checker-executables"></a><a name="index-syntax-checker-executables"></a>
<a name="index-executables-of-syntax-checkers"></a>

<p>Occasionally, you need to point Flycheck to a different executable when
running a syntax checker.  For instance, you might want to use
<code>gcc-4.9</code> to check your C code, or use <code>pylint</code> from a
specific virtualenv.
</p>
<p>For these situations, each syntax checker has a buffer-local,
customizable variable named <code>flycheck-<var>checker</var>-executable</code>,
where <var>checker</var> is the name of the syntax checker.  The value of
this variable is either nil, or a string.  In the former case, Flycheck
uses the default executable from the syntax checker definition when
executing the syntax checker.  In the latter case, it uses the value of
the variable as executable.
</p>
<p>You can either set these variables directly in your init file, or change
them interactively:
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-e"></a>
<a name="index-flycheck_002dset_002dchecker_002dexecutable"></a>
</dd>
<dt><kbd>C-c ! e</kbd></dt>
<dt><kbd>M-x flycheck-set-checker-executable</kbd></dt>
<dd><p>Set the executable of a syntax checker in the current buffer.
</p>
<p>Prompt for a syntax checker and an executable file, and set the
executable variable of the syntax checker.
<a name="index-C_002du-C_002dc-_0021-e"></a>
</p></dd>
<dt><kbd>C-u C-c ! e</kbd></dt>
<dt><kbd>C-u M-x flycheck-set-checker-executable</kbd></dt>
<dd><p>Reset the executable of a syntax checker in the current buffer.
</p>
<p>Prompt for a syntax checker and reset its executable to the default.
</p></dd>
</dl>

<hr>
<a name="Syntax-checker-definitions"></a>
<div class="header">
<p>
Next: <a href="#Flycheck-hooks" accesskey="n" rel="next">Flycheck hooks</a>, Previous: <a href="#Usage" accesskey="p" rel="prev">Usage</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Syntax-checker-definitions-1"></a>
<h2 class="chapter">5 Syntax checker definitions</h2>

<p>This chapter explains how to add new syntax checkers and how to extend
built-in syntax checkers, by example.  See <a href="#Flycheck-API">Flycheck API</a>, for a
detailed reference on the involved types, functions and macros.
</p>
<p>If you define a new syntax checker or have an extension to a built-in
syntax checker, please report it to Flycheck (see <a href="#Issues">Issues</a>), so that
we can consider it for inclusion to make it available to all other users
of Flycheck.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">&bull; <a href="#Defining-syntax-checkers" accesskey="1">Defining syntax checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to define new syntax checkers
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Finding-error-patterns" accesskey="2">Finding error patterns</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to find error patterns for a checker
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Trying-new-checkers" accesskey="3">Trying new checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to try a new syntax checker
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Registering-new-checkers" accesskey="4">Registering new checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to register for automatic selection
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Parsing-structured-output" accesskey="5">Parsing structured output</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to parse structured output like XML
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Passing-configuration-to-checkers" accesskey="6">Passing configuration to checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to make syntax checkers configurable
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Controlling-use-of-checkers" accesskey="7">Controlling use of checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to control when checkers are used
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Applying-multiple-checkers" accesskey="8">Applying multiple checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">How to use more than one checker per buffer
</td></tr>
</table>

<hr>
<a name="Defining-syntax-checkers"></a>
<div class="header">
<p>
Next: <a href="#Finding-error-patterns" accesskey="n" rel="next">Finding error patterns</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Defining-syntax-checkers-1"></a>
<h3 class="section">5.1 Defining syntax checkers</h3>

<p>Flycheck provides the macro <code>flycheck-define-checker</code> to define a
new syntax checker.  The following example defines a simple syntax
checker for the popular <a href="http://batsov.com/rubocop/">Rubocop</a> tool for
Ruby:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker ruby-rubocop
  &quot;A Ruby syntax and style checker using the RuboCop tool.

See URL `http://batsov.com/rubocop/'.&quot;
  :command (&quot;rubocop&quot; &quot;--display-cop-names&quot; &quot;--format&quot; &quot;emacs&quot;
            (config-file &quot;--config&quot; flycheck-rubocoprc)
            (option-flag &quot;--lint&quot; flycheck-rubocop-lint-only)
            &quot;--stdin&quot; source-original)
  :standard-input t
  :error-patterns
  ((info line-start (file-name) &quot;:&quot; line &quot;:&quot; column &quot;: C: &quot;
         (optional (id (one-or-more (not (any &quot;:&quot;)))) &quot;: &quot;) (message) line-end)
   (warning line-start (file-name) &quot;:&quot; line &quot;:&quot; column &quot;: W: &quot;
            (optional (id (one-or-more (not (any &quot;:&quot;)))) &quot;: &quot;) (message)
            line-end)
   (error line-start (file-name) &quot;:&quot; line &quot;:&quot; column &quot;: &quot; (or &quot;E&quot; &quot;F&quot;) &quot;: &quot;
          (optional (id (one-or-more (not (any &quot;:&quot;)))) &quot;: &quot;) (message)
          line-end))
  :modes (enh-ruby-mode ruby-mode)
  :next-checkers ((warning . ruby-rubylint)))
</pre></div>

<p>The first argument to <code>flycheck-define-checker</code> is the <em>name</em>
of a syntax checker, by which we can refer to this particular syntax
checker.
</p>
<p>Next comes the <em>docstring</em>, which should provide a bit of
information about the syntax checker.  It&rsquo;s a good idea to provide a
link to the homepage of the syntax checker tool here.  You can view this
docstring in Emacs with <code>flycheck-describe-checker</code> at
<kbd>C-c ! ?</kbd>, e.g. <kbd>C-c ! ? ruby-rubocop</kbd>.
</p>
<p>Eventually we specify the <em>properties</em> of the new syntax checker.
These properties tell Flycheck when to use your new syntax checker, how
to run it, and how to parse its output:
</p>
<ul>
<li> The <code>:command</code> specifies the command Flycheck should run to check
the buffer.  It&rsquo;s a simple list containing the executable and its
arguments.

<p>In the example above we pass a couple of arguments to <code>rubocop</code>
to configure its output format.  Next come two options:  The special
<code>config-file</code> cell takes the name of a configuration file from the
given variable, searches it and passes the path—if found—to the syntax
checker.  The <code>option-flag</code> cell passes the given argument to the
syntax checker if the given variable is non-nil.
</p>
<p>At last we specify <code>--stdin</code> to make Rubocop read source code
from standard input.  The special <code>source-original</code> symbol gives
the name of the file being checked to Rubocop; Rubocop uses this name in
its error output.
</p>
<p>For a complete list of all special symbols refer to the function
<code>flycheck-substitute-argument</code>.
</p>
</li><li> <code>:standard-input t</code> makes Flycheck send the contents of the buffer
via standard input.  This is the preferred way to pass buffer contents
to syntax checkers.

<p>For syntax checkers that can&rsquo;t read from standard input Flycheck
provides the special <code>source</code> and <code>source-inplace</code> argument
symbols for the <code>:command</code> property.  These argument symbols create
temporary files in the system temp directory or beneath the original
file respectively and give pass them to the syntax checker upon
invocation.
</p>
</li><li> The <code>:error-patterns</code> tell Flycheck how to parse the output of the
command in order to obtain error locations.  Each pattern has a
<em>level</em>, followed by <code>rx</code> forms which specify a regular
expression to find an error in the output of the command.

<p>Flycheck understands three error levels by default: <code>error</code> is for
critical errors that absolutely require the user&rsquo;s attention
(e.g. syntax errors), <code>warning</code> is for issues that can be ignored,
but should not (e.g. unused variables), and <code>info</code> is for other
messages that provide information about the buffer, but do not
immediately require action from the user.
<code>flycheck-define-error-level</code> lets you define custom error levels.
</p>
<p>Flycheck provides special <code>rx</code> forms to extract the relevant
information from each error:
</p>
<ul>
<li> The <code>(file-name)</code> and <code>(message)</code> forms match a sequence of
any character save new line as file name and message of the error.  Both
optionally accept further <code>rx</code> forms, to specify an alternative
regular expression to match the file name or the message, for instance
to parse multi-line error messages.
</li><li> The <code>line</code> and <code>column</code> forms match a sequence of one or more
digits as line and column respectively of the error.
</li></ul>

<p>See the docstring of the function <code>rx</code>, for a list of all standard
<code>rx</code> forms, and the docstring of the function
<code>flycheck-rx-to-string</code> for a list of all special Flycheck forms.
</p>
</li><li> The <code>:modes</code> property denotes the major modes in which Flycheck may
use this syntax checker.  <code>rubocop</code> checks Ruby code, so the
<code>:modes</code> of our example specify <code>ruby-mode</code> and
<code>enh-ruby-mode</code>.

</li></ul>

<hr>
<a name="Finding-error-patterns"></a>
<div class="header">
<p>
Next: <a href="#Trying-new-checkers" accesskey="n" rel="next">Trying new checkers</a>, Previous: <a href="#Defining-syntax-checkers" accesskey="p" rel="prev">Defining syntax checkers</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Finding-the-right-error-patterns"></a>
<h3 class="section">5.2 Finding the right error patterns</h3>

<p>Finding the right error patterns is the hardest part of a syntax checker
definition.  For a first version, you just run the tool on a file, look
at its output and write a regular expression to match it.  <kbd>M-x
shell</kbd> comes handy here.
</p>
<p>However, as you start to debug and refine your patterns, this quickly
becomes cumbersome.  Flycheck provides an easier way to test a syntax
checker: Evaluate the syntax checker definition with <kbd>C-M-x</kbd> and run
<code>flycheck-compile</code>.
</p>
<dl compact="compact">
<dd><a name="index-C_002dc-_0021-C_002dc"></a>
<a name="index-flycheck_002dcompile"></a>
</dd>
<dt><kbd>C-c ! C-c</kbd></dt>
<dt><kbd>M-x flycheck-compile</kbd></dt>
<dd><p>Run a syntax checker on the current buffer in a fresh Compilation Mode
buffer.  Prompt for a syntax checker to run.
</p></dd>
</dl>

<p>This command runs the command like a normal syntax check would do, but
instead of highlighting errors within the buffer it shows a new buffer
in Compilation Mode, which contains the entire output of the command and
highlights everything that matches a pattern.  You can then refine the
error pattern, and iterate through this process until the error pattern
is complete.
</p>
<blockquote class="indentedblock">
<p>The <code>re-builder</code> tool can help you to quickly develop patterns for
the current output.  It lets you interactively develop a regular
expression while continously matching the current expression against the
buffer contents.  Start <code>re-builder</code> with <kbd>M-x re-builder</kbd>, and
switch to the <code>rx</code> syntax with <kbd>C-c TAB</kbd>.  Then type your
<code>rx</code> expression into the small window at the bottom, and observe
how the matching parts of the buffer are highlighted.
</p>
<p>Note that <code>re-builder</code> does <em>not</em> support the special Flycheck
<code>rx</code> forms available in <code>:error-patterns</code>.  As such, you
cannot directly type a Flycheck expression into <code>re-builder</code>.
</p></blockquote>

<p>Sometimes however an output format doesn&rsquo;t lend itself to error
patterns.  In this case, you need to write a more sophisticated parser
yourself.  See <a href="#Parsing-structured-output">Parsing structured output</a>, for more information.
</p>
<hr>
<a name="Trying-new-checkers"></a>
<div class="header">
<p>
Next: <a href="#Registering-new-checkers" accesskey="n" rel="next">Registering new checkers</a>, Previous: <a href="#Finding-error-patterns" accesskey="p" rel="prev">Finding error patterns</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Trying-a-new-syntax-checker"></a>
<h3 class="section">5.3 Trying a new syntax checker</h3>

<p>After evaluating a syntax checker definition you can try whether it
works for normal syntax checks by selecting it manually with <kbd>C-c !
s</kbd> or <kbd>M-x flycheck-select-checker</kbd>.  If anything breaks, you can
unselect the syntax checker again with <kbd>C-u C-c ! s</kbd> and fix the
error without further affecting Flycheck.
</p>
<p>Once you have confirmed that your new syntax checker works flawlessly,
you can make it available for automatic syntax checking by registering
it.
</p>
<hr>
<a name="Registering-new-checkers"></a>
<div class="header">
<p>
Next: <a href="#Parsing-structured-output" accesskey="n" rel="next">Parsing structured output</a>, Previous: <a href="#Trying-new-checkers" accesskey="p" rel="prev">Trying new checkers</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Registering-new-syntax-checkers"></a>
<h3 class="section">5.4 Registering new syntax checkers</h3>

<p>To register a new syntax checker for automatic syntax checking, just add
it to <code>flycheck-checkers</code>:
</p>
<div class="lisp">
<pre class="lisp">(add-to-list 'flycheck-checkers 'python-pylint)
</pre></div>

<p>Flycheck will try all syntax checkers in this variable when checking a
buffer automatically, and check the buffer with the first syntax checker
in this list whose <code>:modes</code> contains the current major mode.
</p>
<blockquote class="indentedblock">
<p>Do <em>not</em> use <code>flycheck-checker</code> and
<code>flycheck-select-checker</code> to enable your own syntax checker in
Flycheck extensions.  They are reserved for <em>user customization</em>.
</p>
<p>Specifically, please do <em>not</em> provide a hook function which selects
the syntax checker explicitly by assigning to <code>flycheck-checker</code> or
by calling <code>flycheck-select-checker</code>.  In other words, this is
<strong>bad</strong>:
</p>
<div class="lisp">
<pre class="lisp">(defun enable-my-new-syntax-checker ()
  (setq flycheck-checker 'my-new-syntax-checker)
  (flycheck-buffer))

(add-hook 'my-major-mode-hook #'enable-my-new-syntax-checker)
</pre></div>

<p>This circumvents the entire automatic selection of Flycheck, and
prevents the user from effectively customizing Flycheck.
</p>
<p>Instead, just register your syntax checker in <code>flycheck-checkers</code>
and let Flycheck automatically pick the best syntax checker.  In other
words, this is <strong>good</strong>:
</p>
<div class="lisp">
<pre class="lisp">(add-to-list 'flycheck-checkers 'my-new-syntax-checker)
</pre></div>
</blockquote>

<hr>
<a name="Parsing-structured-output"></a>
<div class="header">
<p>
Next: <a href="#Passing-configuration-to-checkers" accesskey="n" rel="next">Passing configuration to checkers</a>, Previous: <a href="#Registering-new-checkers" accesskey="p" rel="prev">Registering new checkers</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Parsing-structured-output-1"></a>
<h3 class="section">5.5 Parsing structured output</h3>

<p>If your syntax checker tool offers some structured output format as
alternative to human-readable free text, you can use an
<code>:error-parser</code> function instead of writing an error pattern.  For
instance, <a href="http://www.jshint.com/">JSHint</a> offers the widely spread
Checkstyle XML output format which Flycheck supports out of the box:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker javascript-jshint
  &quot;A JavaScript syntax and style checker using jshint.

See URL `http://www.jshint.com'.&quot;
  :command (&quot;jshint&quot; &quot;--checkstyle-reporter&quot; source)
  :error-parser flycheck-parse-checkstyle
  :modes (js-mode js2-mode js3-mode))
</pre></div>

<p>As you can see, there are no patterns in this definition.  Instead
Flycheck calls the function <code>flycheck-parse-checkstyle</code> to parse
the output.  This function parses the XML to extract the errors.  It&rsquo;s
built-in into Flycheck, so if your tool supports Checkstyle XML, error
parsing comes <em>for free</em> in Flycheck.  See <a href="#Error-parsers">Error parsers</a>,
for more information about error parsers.
</p>
<hr>
<a name="Passing-configuration-to-checkers"></a>
<div class="header">
<p>
Next: <a href="#Controlling-use-of-checkers" accesskey="n" rel="next">Controlling use of checkers</a>, Previous: <a href="#Parsing-structured-output" accesskey="p" rel="prev">Parsing structured output</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Passing-options-and-configuration-files-to-syntax-checkers"></a>
<h3 class="section">5.6 Passing options and configuration files to syntax checkers</h3>

<p>Many linting tools provide a rich set of options to configure their
analysis.  Flycheck makes it easy to define proper Emacs options and map
them to options of commands.
</p>
<p>For instance, the <a href="https://github.com/bbatsov/rubocop">Rubocop</a> tool checks Ruby for
semantic and stylistic issues.  Since style is mainly a matter of taste,
it has a special linting mode in which all stylistic checks are disabled
(error patterns omitted for readability):
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker ruby-rubocop
  &quot;A Ruby syntax and style checker using the RuboCop tool.

See URL `http://batsov.com/rubocop/'.&quot;
  :command (&quot;rubocop&quot; &quot;--format&quot; &quot;emacs&quot;
            (option-flag &quot;--lint&quot; flycheck-rubocop-lint-only)
            source)
  :error-patterns ...
  :modes (ruby-mode))
</pre></div>

<p>Note the special <code>option-flag</code> argument, which splices the value of
the boolean Emacs option <code>flycheck-rubocop-lint-only</code> into the
command: If the variable is non-nil, Flycheck adds the <samp>--lint</samp>
option to the final command line, otherwise Flycheck omits the entire
argument.
</p>
<p>Flycheck also supports other special <code>option-</code> arguments for plain
values or lists of values.  See <a href="#Argument-Substitution">Argument Substitution</a>, for a list of
all special arguments.
</p>
<p>Flycheck also provides a convenience macro
<code>flycheck-def-option-var</code> to declare these options:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-def-option-var flycheck-rubocop-lint-only nil ruby-rubocop
  &quot;Whether to only report code issues in Rubocop.

When non-nil, only report code issues in Rubocop, via `--lint'.
Otherwise report style issues as well.&quot;
  :safe #'booleanp
  :type 'boolean)
</pre></div>

<p>Essentially, this macro is just a wrapper around the built-in
<code>defcustom</code>, which additionally keeps track of the syntax checker
the option belongs to, and adds the option to the appropriate custom
group.  You can pass arbitrary custom keywords to this macro as we did
in this example: <code>:type</code> marks this option as boolean flag, and
<code>:safe</code> allows the use as file-local variable, if the value is
boolean.  See <a href="#Syntax-checker-options">Syntax checker options</a>, for more information about
syntax checker configuration, and <a href="#Checker-configuration">Checker configuration</a>, for the
corresponding API reference.
</p>
<p>By a similar mechanism you can also pass paths to configuration files to
a syntax checker tool.  The aforementioned
<a href="http://www.pylint.org/">Pylint</a> reads a configuration file for
instance:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker python-pylint
  &quot;A Python syntax and style checker using Pylint.

This syntax checker requires Pylint 1.0 or newer.

See URL `http://www.pylint.org/'.&quot;
  ;; -r n disables the scoring report
  :command (&quot;pylint&quot; &quot;-r&quot; &quot;n&quot;
            &quot;--msg-template&quot; &quot;{path}:{line}:{column}:{C}:{msg} ({msg_id})&quot;
            (config-file &quot;--rcfile&quot; flycheck-pylintrc)
            source)
  :error-patterns ...
  :modes python-mode)
</pre></div>

<p>The special <code>config-file</code> argument passes a configuration file from
<code>flycheck-pylintrc</code> to <code>pylint</code>, if the value of the
variable is non-nil.
</p>
<p>Flycheck provides a sophisticated logic to find an appropriate
configuration file.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more
information about syntax checker configuration, and <a href="#Checker-configuration">Checker configuration</a>, for the corresponding API reference.
</p>
<hr>
<a name="Controlling-use-of-checkers"></a>
<div class="header">
<p>
Next: <a href="#Applying-multiple-checkers" accesskey="n" rel="next">Applying multiple checkers</a>, Previous: <a href="#Passing-configuration-to-checkers" accesskey="p" rel="prev">Passing configuration to checkers</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Controlling-the-use-of-a-syntax-checker"></a>
<h3 class="section">5.7 Controlling the use of a syntax checker</h3>

<p>If you need more control about when a syntax checker is used for syntax
checking, you can supply a custom <code>:predicate</code> function.  Consider
the following syntax checker for Zsh scripts in Sh Mode:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker sh-zsh
  &quot;A Zsh syntax checker using the Zsh shell.

See URL `http://www.zsh.org/'.&quot;
  :command (&quot;zsh&quot; &quot;-n&quot; &quot;-d&quot; &quot;-f&quot; source)
  :error-patterns
  ((error line-start (file-name) &quot;:&quot; line &quot;: &quot; (message) line-end))
  :modes sh-mode
  :predicate (lambda () (eq sh-shell 'zsh)))
</pre></div>

<p>Sh Mode also supports Bash and other shells besides Zsh, so we
additionally provide a <code>:predicate</code> that checks whether the current
buffer has the right shell.
</p>
<p>You can even omit <code>:modes</code> and only use a predicate to determine
whether a syntax checker is applicable for the current buffer.
</p>
<hr>
<a name="Applying-multiple-checkers"></a>
<div class="header">
<p>
Previous: <a href="#Controlling-use-of-checkers" accesskey="p" rel="prev">Controlling use of checkers</a>, Up: <a href="#Syntax-checker-definitions" accesskey="u" rel="up">Syntax checker definitions</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Applying-multiple-syntax-checkers"></a>
<h3 class="section">5.8 Applying multiple syntax checkers</h3>

<p>Frequently, we would like to use multiple syntax checkers in a buffer.
For instance, we might want to check the syntax of a script with
<code>sh-zsh</code> from the previous section, and then use
<a href="https://github.com/koalaman/shellcheck/">Shellcheck</a> to check for questionable code
such as unquoted variable expansions, if there are no syntax errors.
Flycheck supports this scenario by <em>chaining</em> syntax checkers.
</p>
<p>Suppose we defined a syntax checker for Shellcheck called
<small>SH-SHELLCHECK</small> as follows:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker sh-shellcheck
  &quot;A shell script syntax and style checker using Shellcheck.

See URL `https://github.com/koalaman/shellcheck/'.&quot;
  :command (&quot;shellcheck&quot; &quot;-f&quot; &quot;checkstyle&quot;
            &quot;-s&quot; (eval (symbol-name sh-shell))
            source)
  :modes sh-mode
  :error-parser flycheck-parse-checkstyle)
</pre></div>

<p>Note how we use the special <code>eval</code> argument to put the result of an
arbitrary Emacs Lisp expression into the command line of
<code>shellcheck</code>, in order to tell Shellcheck what shell the script
is written for.
</p>
<p>We can now arrange for this syntax checker to be used after
<code>sh-zsh</code> with <code>flycheck-add-next-checker</code>:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-add-next-checker 'sh-zsh '(warning . sh-shellcheck))
</pre></div>

<p>The first item of the cons cell in the second argument is the
<em>maximum error level</em> in the buffer, for which <code>sh-shellcheck</code>
is still applicable.  With <code>warning</code> Flycheck will run
<code>sh-shellcheck</code> after <code>sh-zsh</code> if there are <code>warning</code> or
<code>info</code> level errors from <code>sh-zsh</code>, but not if there are any
errors with level <code>error</code>, such as syntax errors.
</p>
<p>Flycheck will only use a chained syntax checker if it is registered in
<code>flycheck-checkers</code>, so we need to register our new syntax checker
(see <a href="#Registering-new-checkers">Registering new checkers</a>):
</p>
<div class="lisp">
<pre class="lisp">(add-to-list 'flycheck-checkers 'sh-shellcheck 'append)
</pre></div>

<p>Note that unlike before we <em>append</em> the new syntax checker at the
end of <code>flycheck-checkers</code>.  This ensures that Flycheck does not
try <code>sh-shellcheck</code> <em>before</em> <code>sh-zsh</code>.  Flycheck tries
all syntax checkers in this list in <em>order of appearance</em>, so if
you add your new chained syntax checker at the beginning, it will likely
be used right away, before any prior syntax checkers.
</p>
<p>You also can specify chained syntax checkers directly in
<code>flycheck-define-checker</code> with the <code>:next-checkers</code> property.
Instead of calling <code>flycheck-add-next-checker</code>, we could also have
added this property to the definition of <code>sh-zsh</code>:
</p>
<div class="lisp">
<pre class="lisp">(flycheck-define-checker sh-zsh
  &quot;A Zsh syntax checker using the Zsh shell.

See URL `http://www.zsh.org/'.&quot;
  :command (&quot;zsh&quot; &quot;-n&quot; &quot;-d&quot; &quot;-f&quot; source)
  :error-patterns ...
  :modes sh-mode
  :predicate (lambda () (eq sh-shell 'zsh))
  :next-checkers ((warning . sh-shellcheck)))
</pre></div>

<p>If you control the definition of both syntax checkers, this style is
<em>preferable</em> to <code>flycheck-add-next-checker</code>.  Use the latter
only if you cannot change the definition of the prior syntax checker.
</p>
<hr>
<a name="Flycheck-hooks"></a>
<div class="header">
<p>
Next: <a href="#Flycheck-API" accesskey="n" rel="next">Flycheck API</a>, Previous: <a href="#Syntax-checker-definitions" accesskey="p" rel="prev">Syntax checker definitions</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Flycheck-hooks-1"></a>
<h2 class="chapter">6 Flycheck hooks</h2>

<p>This chapter gives you a brief overview over Flycheck&rsquo;s rich hook
interface, which you can use for your own extensions.
</p>
<a name="Status-changes"></a>
<h3 class="section">6.1 Status changes</h3>

<p><code>flycheck-before-syntax-check-hook</code> and
<code>flycheck-after-syntax-check-hook</code> run before and after syntax
checks, and let you update your Emacs instance according to Flycheck&rsquo;s
state.  For instance, <a href="https://github.com/flycheck/flycheck-color-mode-line">flycheck-color-mode-line</a> uses these hooks to colour your mode-line
according to the result of the last syntax check.  Additionally,
<code>flycheck-status-changed-functions</code> runs on every single status
change of Flycheck, and provides a fine-grained reporting about what
Flycheck is currently doing.
</p>
<a name="Executables-and-commands"></a>
<h3 class="section">6.2 Executables and commands</h3>

<p>Flycheck uses the function given by the option
<code>flycheck-executable-find</code> to search for executables, and passes
all syntax checker commands through
<code>flycheck-command-wrapper-function</code> before running them.  These
features let you adapt Flycheck to search executables and run commands
in sandboxed environments such as <code>bundle exec</code> or
<code>nix-shell</code>.
</p>
<a name="Error-processing"></a>
<h3 class="section">6.3 Error processing</h3>

<p>The functions in <code>flycheck-process-error-functions</code> are used to
process new errors reported by a Flycheck syntax checker.  Add to this
hook to get informed about each error reported in a Flycheck buffer.  In
fact, Flycheck uses this hook itself: The standard value
<code>flycheck-add-overlay</code> is responsible for adding error highlighting
to the buffer.  As a consequence, you can <em>entirely opt out</em> from
highlighting with a custom hook.
</p>
<a name="Error-display"></a>
<h3 class="section">6.4 Error display</h3>

<p>The function <code>flycheck-display-errors-function</code> is called to
display an error at point.  The <a href="https://github.com/flycheck/flycheck-pos-tip">flycheck-pos-tip</a> extension uses this hook to show errors in a GUI popup
like conventional IDEs do.
</p>
<hr>
<a name="Flycheck-API"></a>
<div class="header">
<p>
Next: <a href="#Supported-languages" accesskey="n" rel="next">Supported languages</a>, Previous: <a href="#Flycheck-hooks" accesskey="p" rel="prev">Flycheck hooks</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Flycheck-API-1"></a>
<h2 class="chapter">7 Flycheck API</h2>

<p>TODO: The API documentation still needs to be written.
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">&bull; <a href="#Command-syntax-checkers" accesskey="1">Command syntax checkers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Syntax checkers with external commands
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Errors" accesskey="2">Errors</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Error representation in Flycheck
</td></tr>
</table>

<hr>
<a name="Command-syntax-checkers"></a>
<div class="header">
<p>
Next: <a href="#Errors" accesskey="n" rel="next">Errors</a>, Up: <a href="#Flycheck-API" accesskey="u" rel="up">Flycheck API</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Command-syntax-checkers-1"></a>
<h3 class="section">7.1 Command syntax checkers</h3>

<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">&bull; <a href="#Argument-Substitution" accesskey="1">Argument Substitution</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Argument substitution in syntax checker commands
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Checker-configuration" accesskey="2">Checker configuration</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Configuration for command checkers
</td></tr>
<tr><td align="left" valign="top">&bull; <a href="#Error-parsers" accesskey="3">Error parsers</a>:</td><td>&nbsp;&nbsp;</td><td align="left" valign="top">Parsing structured output formats
</td></tr>
</table>

<hr>
<a name="Argument-Substitution"></a>
<div class="header">
<p>
Next: <a href="#Checker-configuration" accesskey="n" rel="next">Checker configuration</a>, Up: <a href="#Command-syntax-checkers" accesskey="u" rel="up">Command syntax checkers</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Argument-substitution"></a>
<h4 class="subsection">7.1.1 Argument substitution</h4>

<hr>
<a name="Checker-configuration"></a>
<div class="header">
<p>
Next: <a href="#Error-parsers" accesskey="n" rel="next">Error parsers</a>, Previous: <a href="#Argument-Substitution" accesskey="p" rel="prev">Argument Substitution</a>, Up: <a href="#Command-syntax-checkers" accesskey="u" rel="up">Command syntax checkers</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Configuration-options-and-files"></a>
<h4 class="subsection">7.1.2 Configuration options and files</h4>

<hr>
<a name="Error-parsers"></a>
<div class="header">
<p>
Previous: <a href="#Checker-configuration" accesskey="p" rel="prev">Checker configuration</a>, Up: <a href="#Command-syntax-checkers" accesskey="u" rel="up">Command syntax checkers</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Error-parsers-1"></a>
<h4 class="subsection">7.1.3 Error parsers</h4>

<hr>
<a name="Errors"></a>
<div class="header">
<p>
Previous: <a href="#Command-syntax-checkers" accesskey="p" rel="prev">Command syntax checkers</a>, Up: <a href="#Flycheck-API" accesskey="u" rel="up">Flycheck API</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Errors-1"></a>
<h3 class="section">7.2 Errors</h3>

<hr>
<a name="Supported-languages"></a>
<div class="header">
<p>
Next: <a href="#Getting-Help" accesskey="n" rel="next">Getting Help</a>, Previous: <a href="#Flycheck-API" accesskey="p" rel="prev">Flycheck API</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Supported-languages-1"></a>
<h2 class="appendix">Appendix A Supported languages</h2>

<p>This chapter lists the languages supported by Flycheck.  3rd party
extensions may provide for more languages; please take a look at our
<a href="http://www.flycheck.org/extensions.html">list of extensions</a> for more information.
</p>
<p>Each language has one or more syntax checkers, whose names follow a
convention of &lsquo;<samp><var>language</var>-<var>tool</var></samp>&rsquo; where <var>language</var> is
the programming language checked by the checker, and <var>tool</var> the name
of the checker tool.
</p>
<p>The syntax checkers are listed in the order they are applied to a
buffer.  Use <kbd>C-c ! ?</kbd> (<code>flycheck-describe-checker</code>) to obtain
more information about a syntax checker, and <kbd>C-h v</kbd>
(<code>describe-variable</code>) to read the complete docstring of any option.
</p>

<p>Flycheck supports the following languages:
</p>
<ul>
<li> <a href="#Ada">Ada</a>
</li><li> <a href="#AsciiDoc">AsciiDoc</a>
</li><li> <a href="#C_002fC_002b_002b">C/C++</a>
</li><li> <a href="#CFEngine">CFEngine</a>
</li><li> <a href="#Chef">Chef</a>
</li><li> <a href="#Coffeescript">Coffeescript</a>
</li><li> <a href="#Coq">Coq</a>
</li><li> <a href="#CSS">CSS</a>
</li><li> <a href="#D">D</a>
</li><li> <a href="#Emacs-Lisp">Emacs Lisp</a>
</li><li> <a href="#Erlang">Erlang</a>
</li><li> <a href="#ERuby">ERuby</a>
</li><li> <a href="#Fortran">Fortran</a>
</li><li> <a href="#Go">Go</a>
</li><li> <a href="#Groovy">Groovy</a>
</li><li> <a href="#Haml">Haml</a>
</li><li> <a href="#Handlebars">Handlebars</a>
</li><li> <a href="#Haskell">Haskell</a>
</li><li> <a href="#HTML">HTML</a>
</li><li> <a href="#Jade">Jade</a>
</li><li> <a href="#Javascript">Javascript</a>
</li><li> <a href="#JSON">JSON</a>
</li><li> <a href="#Less">Less</a>
</li><li> <a href="#Lua">Lua</a>
</li><li> <a href="#Perl">Perl</a>
</li><li> <a href="#PHP">PHP</a>
</li><li> <a href="#Processing">Processing</a>
</li><li> <a href="#Puppet">Puppet</a>
</li><li> <a href="#Python">Python</a>
</li><li> <a href="#R">R</a>
</li><li> <a href="#Racket">Racket</a>
</li><li> <a href="#RPM-Spec">RPM Spec</a>
</li><li> <a href="#reStructuredText">reStructuredText</a>
</li><li> <a href="#Ruby">Ruby</a>
</li><li> <a href="#Rust">Rust</a>
</li><li> <a href="#Sass">Sass</a>
</li><li> <a href="#Scala">Scala</a>
</li><li> <a href="#SCSS">SCSS</a>
</li><li> <a href="#Shell-scripting-languages">Shell scripting languages</a>
</li><li> <a href="#Slim">Slim</a>
</li><li> <a href="#SQL">SQL</a>
</li><li> <a href="#TeX_002fLaTeX">TeX/LaTeX</a>
</li><li> <a href="#Texinfo">Texinfo</a>
</li><li> <a href="#Verilog">Verilog</a>
</li><li> <a href="#XML">XML</a>
</li><li> <a href="#YAML">YAML</a>
</li></ul>

<a name="Ada"></a><a name="Ada-1"></a>
<h3 class="unnumberedsec">Ada</h3>
<a name="index-Language_002c-Ada"></a>
<a name="index-Ada-language"></a>

<ul>
<li> <code>ada-gnat</code>
(<a href="https://gcc.gnu.org/onlinedocs/gnat_ugn_unw/">GNAT</a>), with the
following options:

<dl compact="compact">
<dt><code>flycheck-gnat-args</code></dt>
<dd><a name="index-flycheck_002dgnat_002dargs"></a>
<p>A list of additional arguments to GNAT.
</p></dd>
<dt><code>flycheck-gnat-include-path</code></dt>
<dd><a name="index-flycheck_002dgnat_002dinclude_002dpath"></a>
<p>A list of include directories for GNAT.  Relative paths are relative to
the file being checked.
</p></dd>
<dt><code>flycheck-gnat-language-standard</code></dt>
<dd><a name="index-flycheck_002dgnat_002dlanguage_002dstandard"></a>
<p>The language standard to use in GNAT, as string.
</p></dd>
<dt><code>flycheck-gnat-warnings</code></dt>
<dd><a name="index-flycheck_002dgnat_002dwarnings"></a>
<p>A list of additional warnings to enable in GNAT.  Each item is the name
of a warning category to enable.
</p></dd>
</dl>

</li></ul>

<a name="AsciiDoc"></a><a name="AsciiDoc-1"></a>
<h3 class="unnumberedsec">AsciiDoc</h3>
<a name="index-Language_002c-AsciiDoc"></a>
<a name="index-AsciiDoc-language"></a>

<ul>
<li> <code>asciidoc</code> (<a href="http://www.methods.co.nz/asciidoc">AsciiDoc</a>)
</li></ul>

<a name="C_002fC_002b_002b"></a><a name="C_002fC_002b_002b-1"></a>
<h3 class="unnumberedsec">C/C++</h3>
<a name="index-Language_002c-C_002fC_002b_002b"></a>
<a name="index-C_002fC_002b_002b-language"></a>

<ol>
<li> <code>c/c++-clang</code> (syntax and type check with
<a href="http://clang.llvm.org/">Clang</a>) or <code>c/c++-gcc</code> (syntax and
type check with <a href="https://gcc.gnu.org/">GCC</a>), and
</li><li> <code>c/c++-cppcheck</code> (style and error check with
<a href="http://cppcheck.sourceforge.net/">cppcheck</a>).
</li></ol>

<p><code>c/c++-clang</code> and <code>c/c++-gcc</code> provide the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-clang-args</code></dt>
<dd><a name="index-flycheck_002dclang_002dargs"></a>
</dd>
<dt><code>flycheck-gcc-args</code></dt>
<dd><a name="index-flycheck_002dgcc_002dargs"></a>
<p>A list of additional arguments for Clang/GCC.
</p></dd>
<dt><code>flycheck-clang-blocks</code></dt>
<dd><a name="index-flycheck_002dclang_002dblocks"></a>
<p>Whether to enable blocks in Clang.
</p></dd>
<dt><code>flycheck-clang-definitions</code></dt>
<dd><a name="index-flycheck_002dclang_002ddefinitions"></a>
</dd>
<dt><code>flycheck-gcc-definitions</code></dt>
<dd><a name="index-flycheck_002dgcc_002ddefinitions"></a>
<p>A list of additional preprocessor definitions for Clang/GCC.
</p></dd>
<dt><code>flycheck-clang-include-path</code></dt>
<dd><a name="index-flycheck_002dclang_002dinclude_002dpath"></a>
</dd>
<dt><code>flycheck-gcc-include-path</code></dt>
<dd><a name="index-flycheck_002dgcc_002dinclude_002dpath"></a>
<p>A list of include directories for Clang/GCC, relative to the file being
checked.
</p></dd>
<dt><code>flycheck-clang-includes</code></dt>
<dd><a name="index-flycheck_002dclang_002dincludes"></a>
</dd>
<dt><code>flycheck-gcc-includes</code></dt>
<dd><a name="index-flycheck_002dgcc_002dincludes"></a>
<p>A list of additional include files for Clang/GCC, relative to the file
being checked.
</p></dd>
<dt><code>flycheck-clang-language-standard</code></dt>
<dd><a name="index-flycheck_002dclang_002dlanguage_002dstandard"></a>
</dd>
<dt><code>flycheck-gcc-language-standard</code></dt>
<dd><a name="index-flycheck_002dgcc_002dlanguage_002dstandard"></a>
<p>The language standard to use in Clang/GCC, as string, via the
<samp>-std</samp> option.
</p></dd>
<dt><code>flycheck-clang-ms-extensions</code></dt>
<dd><a name="index-flycheck_002dclang_002dms_002dextensions"></a>
<p>Whether to enable Microsoft extensions to C/C++ in Clang.
</p></dd>
<dt><code>flycheck-clang-no-exceptions</code></dt>
<dd><a name="index-flycheck_002dclang_002dno_002dexceptions"></a>
</dd>
<dt><code>flycheck-gcc-no-exceptions</code></dt>
<dd><a name="index-flycheck_002dgcc_002dno_002dexceptions"></a>
<p>Whether to disable exceptions in Clang/GCC.
</p></dd>
<dt><code>flycheck-clang-no-rtti</code></dt>
<dd><a name="index-flycheck_002dclang_002dno_002drtti"></a>
</dd>
<dt><code>flycheck-gcc-no-rtti</code></dt>
<dd><a name="index-flycheck_002dgcc_002dno_002drtti"></a>
<p>Whether to disable RTTI in Clang/GCC, via <samp>-fno-rtti</samp>.
</p></dd>
<dt><code>flycheck-clang-standard-library</code></dt>
<dd><a name="index-flycheck_002dclang_002dstandard_002dlibrary"></a>
<p>The name of the standard library to use for Clang, as string.
</p></dd>
<dt><code>flycheck-gcc-openmp</code></dt>
<dd><a name="index-flycheck_002dgcc_002dopenmp"></a>
<p>Whether to enable OpenMP in GCC.
</p></dd>
<dt><code>flycheck-clang-pedantic</code></dt>
<dd><a name="index-flycheck_002dclang_002dpedantic"></a>
</dd>
<dt><code>flycheck-gcc-pedantic</code></dt>
<dd><a name="index-flycheck_002dgcc_002dpedantic"></a>
<p>Whether to warn about language extensions in Clang/GCC.
</p></dd>
<dt><code>flycheck-clang-pedantic-errors</code></dt>
<dd><a name="index-flycheck_002dclang_002dpedantic_002derrors"></a>
</dd>
<dt><code>flycheck-gcc-pedantic-errors</code></dt>
<dd><a name="index-flycheck_002dgcc_002dpedantic_002derrors"></a>
<p>Whether to error on language extensions in Clang/GCC.
</p></dd>
<dt><code>flycheck-clang-warnings</code></dt>
<dd><a name="index-flycheck_002dclang_002dwarnings"></a>
</dd>
<dt><code>flycheck-gcc-warnings</code></dt>
<dd><a name="index-flycheck_002dgcc_002dwarnings"></a>
<p>A list of additional warnings to enable in Clang.  Each item is the name
of a warning or warning category for <samp>-W</samp>.
</p></dd>
</dl>

<p><code>c/c++-cppcheck</code> provides the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-cppcheck-checks</code></dt>
<dd><a name="index-flycheck_002dcppcheck_002dchecks"></a>
<p>A list of enabled checks for cppcheck.  Each item is the name of a
check for the <samp>--enable</samp> option.
</p></dd>
<dt><code>flycheck-cppcheck-inconclusive</code></dt>
<dd><a name="index-flycheck_002dcppcheck_002dinconclusive"></a>
<p>Whether to enable inconclusive checks in cppcheck.  These checks may
yield more false positives than normal checks.
</p></dd>
<dt><code>flycheck-cppcheck-include-path</code></dt>
<dd><a name="index-flycheck_002dcppcheck_002dinclude_002dpath"></a>
<p>A list of include directories for cppcheck.  Relative paths are relative to
the file being checked.
</p></dd>
<dt><code>flycheck-cppcheck-language-standard</code></dt>
<dd><a name="index-flycheck_002dcppcheck_002dlanguage_002dstandard"></a>
<p>The C or C++ language standard to use with cppcheck via <samp>--std=</samp>.
</p></dd>
</dl>

<a name="CFEngine"></a><a name="CFEngine-1"></a>
<h3 class="unnumberedsec">CFEngine</h3>
<a name="index-Language_002c-CFEngine"></a>
<a name="index-CFEngine-language"></a>

<ul>
<li> <code>cfengine</code> (<a href="http://cfengine.com/">CFEngine</a>)
</li></ul>

<a name="Chef"></a><a name="Chef-1"></a>
<h3 class="unnumberedsec">Chef</h3>
<a name="index-Language_002c-Chef"></a>
<a name="index-Chef-language"></a>

<ul>
<li> <code>chef-foodcritic</code> (style check with
<a href="http://acrmp.github.io/foodcritic/">foodcritic</a>), with the
following option:

<dl compact="compact">
<dt><code>flycheck-foodcritic-tags</code></dt>
<dd><a name="index-flycheck_002dfoodcritic_002dtags"></a>
<p>A list of tags to select for Foodcritic.
</p></dd>
</dl>

</li></ul>

<a name="Coffeescript"></a><a name="Coffeescript-1"></a>
<h3 class="unnumberedsec">Coffeescript</h3>
<a name="index-Language_002c-Coffeescript"></a>
<a name="index-Coffeescript-language"></a>

<ol>
<li> <code>coffee</code> (syntax check with <a href="http://coffeescript.org/">coffee</a>)
</li><li> <code>coffee-coffeelint</code> (code style check with
<a href="http://www.coffeelint.org/">coffeelint</a>), with the following
option:

<dl compact="compact">
<dt><code>flycheck-coffeelintrc</code></dt>
<dd><a name="index-flycheck_002dcoffeelintrc"></a>
<p>Configuration file for coffeelint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

</li></ol>

<a name="Coq"></a><a name="Coq-1"></a>
<h3 class="unnumberedsec">Coq</h3>
<a name="index-Language_002c-Coq"></a>
<a name="index-Coq-language"></a>

<ul>
<li> <code>coq</code> (<a href="http://coq.inria.fr/">Coq</a>)
</li></ul>

<a name="CSS"></a><a name="CSS-1"></a>
<h3 class="unnumberedsec">CSS</h3>
<a name="index-Language_002c-CSS"></a>
<a name="index-CSS-language"></a>

<ul>
<li> <code>css-csslint</code> (style and error check with
<a href="https://github.com/CSSLint/csslint">CSSLint</a>)
</li></ul>

<a name="D"></a><a name="D-1"></a>
<h3 class="unnumberedsec">D</h3>
<a name="index-Language_002c-D"></a>
<a name="index-D-language"></a>

<ul>
<li> <code>d-dmd</code> (<a href="http://dlang.org/">DMD</a>), with the following options:

<dl compact="compact">
<dt><code>flycheck-dmd-include-path</code></dt>
<dd><a name="index-flycheck_002ddmd_002dinclude_002dpath"></a>
<p>A list of include directories for DMD.
</p></dd>
<dt><code>flycheck-dmd-args</code></dt>
<dd><a name="index-flycheck_002ddmd_002dargs"></a>
<p>A list of additional arguments for DMD.
</p></dd>
</dl>

</li></ul>

<blockquote class="smallindentedblock">
<p>The extension <a href="https://github.com/flycheck/flycheck-d-unittest">flycheck-d-unittest</a>
adds a syntax checker which runs D unittests on the fly and reports the
results.
</p></blockquote>

<a name="Emacs-Lisp"></a><a name="Emacs-Lisp-1"></a>
<h3 class="unnumberedsec">Emacs Lisp</h3>
<a name="index-Language_002c-Emacs-Lisp"></a>
<a name="index-Emacs-Lisp-language"></a>

<ol>
<li> <code>emacs-lisp</code> (syntax check with the built-in Emacs byte compiler)
</li><li> <code>emacs-lisp-checkdoc</code> (code and documentation check with
<code>checkdoc</code>)
</li></ol>

<blockquote class="smallindentedblock">
<p>The extension <a href="https://github.com/purcell/flycheck-package">flycheck-package</a> adds a
syntax checker which checks for violations of Emacs Lisp packaging
conventions.
</p></blockquote>

<p>The <code>emacs-lisp</code> checker provides the following options
</p>
<dl compact="compact">
<dt><code>flycheck-emacs-lisp-load-path</code></dt>
<dd><a name="index-flycheck_002demacs_002dlisp_002dload_002dpath"></a>
<p>The load path to use while checking Emacs Lisp files, as list of
strings.  Relative directories are expanded against the
<code>default-directory</code> of the buffer being checked.
</p>
</dd>
<dt><code>flycheck-emacs-lisp-initialize-packages</code></dt>
<dd><a name="index-flycheck_002demacs_002dlisp_002dinitialize_002dpackages"></a>
<p>Whether to initialize Emacs&rsquo; package manager with
<code>package-initialize</code> before checking the buffer.  If set to
<code>auto</code> (the default), only initialize the package managers for
files in under <code>user-emacs-directory</code>.
</p>
</dd>
<dt><code>flycheck-emacs-lisp-package-user-dir</code></dt>
<dd><a name="index-flycheck_002demacs_002dlisp_002dpackage_002duser_002ddir"></a>
<p>The package directory for the Emacs Lisp checker, as string.  Has no
effect if <code>flycheck-emacs-lisp-initialize-packages</code> is nil.
</p></dd>
</dl>

<a name="Erlang"></a><a name="Erlang-1"></a>
<h3 class="unnumberedsec">Erlang</h3>
<a name="index-Language_002c-Erlang"></a>
<a name="index-Erlang-language"></a>

<ul>
<li> <code>erlang</code> (<a href="http://www.erlang.org/">Erlang</a>)

<dl compact="compact">
<dt><code>flycheck-erlang-include-path</code></dt>
<dd><a name="index-flycheck_002derlang_002dinclude_002dpath"></a>
<p>A list of include directories for Erlang.
</p>
</dd>
<dt><code>flycheck-erlang-library-path</code></dt>
<dd><a name="index-flycheck_002derlang_002dlibrary_002dpath"></a>
<p>A list of library directories for Erlang.
</p></dd>
</dl>

</li></ul>

<a name="ERuby"></a><a name="ERuby-1"></a>
<h3 class="unnumberedsec">ERuby</h3>
<a name="index-Language_002c-ERuby"></a>
<a name="index-ERuby-language"></a>

<ul>
<li> <code>eruby-erubis</code>
(<a href="http://www.kuwata-lab.com/erubis/"><code>erubis</code></a>)
</li></ul>

<a name="Fortran"></a><a name="Fortran-1"></a>
<h3 class="unnumberedsec">Fortran</h3>
<a name="index-Language_002c-Fortran"></a>
<a name="index-Fortran-language"></a>

<ol>
<li> <code>fortran-gfortran</code>
(<a href="https://gcc.gnu.org/onlinedocs/gfortran/">GFortran</a>), with the
following options:

<dl compact="compact">
<dt><code>flycheck-gfortran-args</code></dt>
<dd><a name="index-flycheck_002dgfortran_002dargs"></a>
<p>A list of additional arguments to GFortran.
</p>
</dd>
<dt><code>flycheck-gfortran-include-path</code></dt>
<dd><a name="index-flycheck_002dgfortran_002dinclude_002dpath"></a>
<p>A list of include directories for GFortran.  Relative paths are relative
to the file being checked.
</p>
</dd>
<dt><code>flycheck-gfortran-language-standard</code></dt>
<dd><a name="index-flycheck_002dgfortran_002dlanguage_002dstandard"></a>
<p>The language standard to use with GFortran, for the <samp>-std</samp>
option.
</p>
</dd>
<dt><code>flycheck-gfortran-layout</code></dt>
<dd><a name="index-flycheck_002dgfortran_002dlayout"></a>
<p>The source code layout to use with GFortran.  Set to <code>free</code> or
<code>fixed</code> for free or fixed layout respectively, or nil (the default)
to let GFortran automatically determine the layout.
</p>
</dd>
<dt><code>flycheck-gfortran-warnings</code></dt>
<dd><a name="index-flycheck_002dgfortran_002dwarnings"></a>
<p>A list of warnings enabled for GFortran, via the <samp>-W</samp> option.
</p></dd>
</dl>

</li></ol>

<a name="Go"></a><a name="Go-1"></a>
<h3 class="unnumberedsec">Go</h3>
<a name="index-Language_002c-Go"></a>
<a name="index-Go-language"></a>

<ol>
<li> <code>go-gofmt</code> (syntax check with
<a href="http://golang.org/cmd/gofmt/">gofmt</a>)
</li><li> <code>go-golint</code> (coding style with
<a href="https://github.com/golang/lint">Golint</a>)
</li><li> <code>go-vet</code> (check for suspicious code with
<a href="http://godoc.org/golang.org/x/tools/cmd/vet"><code>go tool
vet</code></a>)
</li><li> <code>go-build</code> or <code>go-test</code> (syntax and type check with
<a href="http://golang.org/cmd/go">Go</a>, for source and tests
respectively)
</li><li> <code>go-errcheck</code> (check for unhandled error returns with
<a href="https://github.com/kisielk/errcheck">errcheck</a>)
</li></ol>

<p><code>go-vet</code> provides the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-go-build-install-deps</code></dt>
<dd><a name="index-flycheck_002dgo_002dbuild_002dinstall_002ddeps"></a>
<p>Whether to install dependencies while checking with <code>go build</code>.
</p>
</dd>
<dt><code>flycheck-go-build-tags</code></dt>
<dd><a name="index-flycheck_002dgo_002dbuild_002dtags"></a>
<p>A list of tags for <code>go build</code>.
</p>
</dd>
<dt><code>flycheck-go-vet-print-functions</code></dt>
<dd><a name="index-flycheck_002dgo_002dvet_002dprint_002dfunctions"></a>
<p>A list of print-like functions for go vet.  Go vet will check these
functions for format string problems.
</p>
</dd>
<dt><code>flycheck-go-vet-shadow</code></dt>
<dd><a name="index-flycheck_002dgo_002dvet_002dshadow"></a>
<p>Whether to check for shadowed variables in go vet, in Go 1.6 or newer.
</p>
</dd>
</dl>

<a name="Groovy"></a><a name="Groovy-1"></a>
<h3 class="unnumberedsec">Groovy</h3>
<a name="index-Language_002c-Groovy"></a>
<a name="index-Groovy-language"></a>

<ul>
<li> <code>groovy</code> (syntax check using groovy compiler API (<a href="http://www.groovy-lang.org/">http://www.groovy-lang.org/</a>))

</li></ul>

<a name="Haml"></a><a name="Haml-1"></a>
<h3 class="unnumberedsec">Haml</h3>
<a name="index-Language_002c-Haml"></a>
<a name="index-Haml-language"></a>

<ul>
<li> <code>haml</code> (<a href="http://haml.info/">Haml</a>)
</li></ul>

<a name="Handlebars"></a><a name="Handlebars-1"></a>
<h3 class="unnumberedsec">Handlebars</h3>
<a name="index-Language_002c-Handlebars"></a>
<a name="index-Handlebars-language"></a>

<ul>
<li> <code>handlebars</code> (<a href="http://handlebarsjs.com/">Handlebars</a>)
</li></ul>

<a name="Haskell"></a><a name="Haskell-1"></a>
<h3 class="unnumberedsec">Haskell</h3>
<a name="index-Language_002c-Haskell"></a>
<a name="index-Haskell-language"></a>

<ol>
<li> <ul>
<li> <code>haskell-stack-ghc</code> (syntax and type checker using
<a href="https://github.com/commercialhaskell/stack">Stack</a>) in Stack
projects, or
</li><li> <code>haskell-ghc</code> (syntax and type checker with
<a href="http://www.haskell.org/ghc/">GHC</a>),
</li></ul>

</li><li> and <code>haskell-hlint</code> (style checker with
<a href="https://github.com/ndmitchell/hlint">hlint</a>), with the
following options:

<dl compact="compact">
<dt><code>flycheck-hlint-args</code></dt>
<dd><a name="index-flycheck_002dhlint_002dargs"></a>
<p>A list of additional arguments for Hlint.
</p>
</dd>
<dt><code>flycheck-hlint-language-extensions</code></dt>
<dd><a name="index-flycheck_002dhlint_002dlanguage_002dextensions"></a>
<p>Extensions list.
</p>
</dd>
<dt><code>flycheck-hlint-ignore-rules</code></dt>
<dd><a name="index-flycheck_002dhlint_002dignore_002drules"></a>
<p>Ignore rules list.
</p>
</dd>
<dt><code>flycheck-hlint-hint-packages</code></dt>
<dd><a name="index-flycheck_002dhlint_002dhint_002dpackages"></a>
<p>Hint packages to include.
</p></dd>
</dl>

<dl compact="compact">
<dt><code>flycheck-hlintrc</code></dt>
<dd><a name="index-flycheck_002dhlintrc"></a>
<p>Configuration file for hlint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

</li></ol>

<blockquote class="smallindentedblock">
<p>The extension <a href="https://github.com/flycheck/flycheck-haskell">flycheck-haskell</a>
configures Flycheck from the current Cabal project, and adds support for
Cabal sandboxes.  The extension
<a href="https://github.com/flycheck/flycheck-hdevtools">flycheck-hdevtools</a> adds an
alternative syntax checker for <code>haskell-ghc</code> using
<a href="https://github.com/bitc/hdevtools/">hdevtools</a>.
</p></blockquote>

<p>The <code>haskell-ghc</code> checker provides the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-ghc-args</code></dt>
<dd><a name="index-flycheck_002dghc_002dargs"></a>
<p>A list of additional arguments for GHC.
</p>
</dd>
<dt><code>flycheck-ghc-no-user-package-database</code></dt>
<dd><a name="index-flycheck_002dghc_002dno_002duser_002dpackage_002ddatabase"></a>
<p>Whether to disable the user package database in GHC.
</p>
</dd>
<dt><code>flycheck-ghc-package-databases</code></dt>
<dd><a name="index-flycheck_002dghc_002dpackage_002ddatabases"></a>
<p>A list of additional package databases for GHC.  Each item points to a
directory containing a package directory, for the <samp>-package-db</samp>
option.
</p>
</dd>
<dt><code>flycheck-ghc-search-path</code></dt>
<dd><a name="index-flycheck_002dghc_002dsearch_002dpath"></a>
<p>A list of module directories for GHC, via the <samp>-i</samp> option.
</p>
</dd>
<dt><code>flycheck-ghc-language-extensions</code></dt>
<dd><a name="index-flycheck_002dghc_002dlanguage_002dextensions"></a>
<p>A list of language extensions for GHC, via <samp>-X</samp>.
</p></dd>
</dl>

<a name="HTML"></a><a name="HTML-1"></a>
<h3 class="unnumberedsec">HTML</h3>
<a name="index-Language_002c-HTML"></a>
<a name="index-HTML-language"></a>

<ul>
<li> <code>html-tidy</code> (<a href="https://github.com/w3c/tidy-html5">Tidy HTML5</a>),
with the following option:

<dl compact="compact">
<dt><code>flycheck-tidyrc</code></dt>
<dd><a name="index-flycheck_002dtidyrc"></a>
<p>Configuration file for Tidy.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

</li></ul>

<a name="Jade"></a><a name="Jade-1"></a>
<h3 class="unnumberedsec">Jade</h3>
<a name="index-Language_002c-Jade"></a>
<a name="index-Jade-language"></a>

<ul>
<li> <code>jade</code> (using <a href="http://jade-lang.com/">Jade</a>)
</li></ul>

<a name="Javascript"></a><a name="Javascript-1"></a>
<h3 class="unnumberedsec">Javascript</h3>
<a name="index-Language_002c-Javascript"></a>
<a name="index-Javascript-language"></a>

<ol>
<li> <ul>
<li> <code>javascript-jshint</code> (<a href="http://jshint.com/">JSHint</a>),
</li><li> or <code>javascript-eslint</code> (<a href="http://eslint.org/">ESLint</a>),
</li><li> or <code>javascript-gjslint</code>
(<a href="https://developers.google.com/closure/utilities">Closure Linter</a>)
</li></ul>
</li><li> <code>javascript-jscs</code> (<a href="http://jscs.info/">JSCS</a>)
</li><li> <code>javascript-standard</code>
(<a href="https://github.com/feross/standard">Standard</a> or
<a href="https://github.com/Flet/semistandard">Semistandard</a>)
</li></ol>

<p>These checkers provide the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-eslint-rulesdir</code></dt>
<dd><a name="index-flycheck_002deslint_002drulesdir"></a>
<p>A directory with custom rules for ESLint.
</p></dd>
<dt><code>flycheck-jshint-extract-javascript</code></dt>
<dd><a name="index-flycheck_002djshint_002dextract_002djavascript"></a>
<p>Whether to extract Javascript from HTML before linting with JSHint.
</p></dd>
<dt><code>flycheck-eslintrc</code></dt>
<dd><a name="index-flycheck_002deslintrc"></a>
<p>Configuration file for ESLint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-jshintrc</code></dt>
<dd><a name="index-flycheck_002djshintrc"></a>
<p>Configuration file for JSHint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-gjslintrc</code></dt>
<dd><a name="index-flycheck_002dgjslintrc"></a>
<p>Configuration file for Closure Linter.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-jscsrc</code></dt>
<dd><a name="index-flycheck_002djscsrc"></a>
<p>Configuration file for JSCS.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<a name="JSON"></a><a name="JSON-1"></a>
<h3 class="unnumberedsec">JSON</h3>
<a name="index-Language_002c-JSON"></a>
<a name="index-JSON-language"></a>

<ul>
<li> <code>json-jsonlint</code> (<a href="https://github.com/zaach/jsonlint">jsonlint</a>)
</li><li> or <code>json-python-json</code>
(<a href="https://docs.python.org/3.5/library/json.html">Python json.tool module</a>)
</li></ul>

<a name="Less"></a><a name="Less-1"></a>
<h3 class="unnumberedsec">Less</h3>
<a name="index-Language_002c-Less"></a>
<a name="index-Less-language"></a>

<ul>
<li> <code>less</code> (<a href="http://lesscss.org/">less</a>)
</li></ul>

<a name="Lua"></a><a name="Lua-1"></a>
<h3 class="unnumberedsec">Lua</h3>
<a name="index-Language_002c-Lua"></a>
<a name="index-Lua-language"></a>

<ul>
<li> <code>luacheck</code> (<a href="https://github.com/mpeterv/luacheck">Luacheck</a>)
with the following option:

<dl compact="compact">
<dt><code>flycheck-luacheckrc</code></dt>
<dd><a name="index-flycheck_002dluacheckrc"></a>
<p>Configuration file for Luacheck.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

</li><li> <code>lua</code> (<a href="http://www.lua.org/">Lua compiler</a>)
</li></ul>

<a name="Perl"></a><a name="Perl-1"></a>
<h3 class="unnumberedsec">Perl</h3>
<a name="index-Language_002c-Perl"></a>
<a name="index-Perl-language"></a>

<ol>
<li> <code>perl</code> (syntax check with the <a href="http://www.perl.org/">Perl
interpreter</a>)
</li><li> <code>perl-perlcritic</code> (style and code check with
<a href="https://metacpan.org/pod/Perl::Critic">Perl::Critic</a>)
</li></ol>

<p>These syntax checkers checker provide the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-perl-include-path</code></dt>
<dd><a name="index-flycheck_002dperl_002dinclude_002dpath"></a>
<p>A list of include directories for Perl, relative to the file being
checked.
</p></dd>
<dt><code>flycheck-perlcriticrc</code></dt>
<dd><a name="index-flycheck_002dperlcriticrc"></a>
<p>Configuration file for Perl::Critic.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-perlcritic-severity</code></dt>
<dd><a name="index-flycheck_002dperlcritic_002dseverity"></a>
<p>The severity level for Perl::Critic, as integer for the
<samp>--severity</samp> option of Perl::Critic.
</p></dd>
</dl>

<a name="PHP"></a><a name="PHP-1"></a>
<h3 class="unnumberedsec">PHP</h3>
<a name="index-Language_002c-PHP"></a>
<a name="index-PHP-language"></a>

<ol>
<li> <code>php</code> (syntax check with
<a href="http://php.net/manual/en/features.commandline.php">PHP CLI</a>)
</li><li> <code>php-phpmd</code> (code check with <a href="http://phpmd.org/">PHP Mess
Detector</a>)
</li><li> <code>php-phpcs</code> (style check with
<a href="http://pear.php.net/package/PHP_CodeSniffer/">PHP CodeSniffer</a>)
</li></ol>

<p>These checkers provide the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-phpmd-rulesets</code></dt>
<dd><a name="index-flycheck_002dphpmd_002drulesets"></a>
<p>A list of rule sets for PHP Mess Detector as strings.  Each item is
either the name of a default rule set, or the path to a custom rule set
file.
</p>
</dd>
<dt><code>flycheck-phpcs-standard</code></dt>
<dd><a name="index-flycheck_002dphpcs_002dstandard"></a>
<p>The coding standard for PHP CodeSniffer, either as name of a built-in
standard, or as path to a standard specification.
</p></dd>
</dl>

<a name="Processing"></a><a name="Processing-1"></a>
<h3 class="unnumberedsec">Processing</h3>
<a name="index-Language_002c-Processing"></a>
<a name="index-Processing-language"></a>

<ul>
<li> <code>processing</code> (using the <a href="https://processing.org/">Processing
command-line tool</a>)
</li></ul>

<a name="Puppet"></a><a name="Puppet-1"></a>
<h3 class="unnumberedsec">Puppet</h3>
<a name="index-Language_002c-Puppet"></a>
<a name="index-Puppet-language"></a>

<ul>
<li> <code>puppet-parser</code> (syntax check with <a href="http://puppetlabs.com/">Puppet</a>)
</li><li> <code>puppet-lint</code> (style check with <a href="http://puppet-lint.com/">Puppet Lint</a>)
</li></ul>

<p><code>puppet-lint</code> provides the following options:
</p><dl compact="compact">
<dt><code>flycheck-puppet-lint-rc</code></dt>
<dd><a name="index-flycheck_002dpuppet_002dlint_002drc"></a>
<p>Configuration file for puppet-lint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-puppet-lint-disabled-checks</code></dt>
<dd><a name="index-flycheck_002dpuppet_002dlint_002ddisabled_002dchecks"></a>
<p>A list of Puppet Lint checks to disable.
</p></dd>
</dl>

<a name="Python"></a><a name="Python-1"></a>
<h3 class="unnumberedsec">Python</h3>
<a name="index-Language_002c-Python"></a>
<a name="index-Python-language"></a>

<ul>
<li> <code>python-flake8</code> (syntax and style checking with
<a href="https://pypi.python.org/pypi/flake8">flake8</a>), or
</li><li> <code>python-pylint</code> (syntax and style checking with
<a href="http://pylint.org/">Pylint</a>), or
</li><li> <code>python-pycompile</code> (syntax checking with Python&rsquo;s
<a href="https://docs.python.org/3.4/library/py_compile.html">built-in byte
compiler</a>, as last resort)
</li></ul>

<blockquote class="smallindentedblock">
<p>The extension <a href="https://github.com/Wilfred/flycheck-pyflakes">flycheck-pyflakes</a> adds a
syntax checker using
<a href="https://pypi.python.org/pypi/pyflakes">Pyflakes</a>.
</p></blockquote>

<p><code>python-flake8</code> provides the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-flake8-error-level-alist</code></dt>
<dd><a name="index-flycheck_002dflake8_002derror_002dlevel_002dalist"></a>
<p>An alist mapping Flake8 error IDs to Flycheck error levels.
</p>
</dd>
<dt><code>flycheck-flake8-maximum-complexity</code></dt>
<dd><a name="index-flycheck_002dflake8_002dmaximum_002dcomplexity"></a>
<p>The maximum McCabe complexity of methods allowed by Flake8.
</p>
</dd>
<dt><code>flycheck-flake8-maximum-line-length</code></dt>
<dd><a name="index-flycheck_002dflake8_002dmaximum_002dline_002dlength"></a>
<p>The maximum length of lines for Flake8.
</p>
</dd>
<dt><code>flycheck-flake8rc</code></dt>
<dd><a name="index-flycheck_002dflake8rc"></a>
<p>Configuration file for Flake8.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<p><code>python-pylint</code> provides the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-pylint-use-symbolic-id</code></dt>
<dd><a name="index-flycheck_002dpylint_002duse_002dsymbolic_002did"></a>
<p>A boolean indicating whether to report symbolic or numeric message identifiers.
For example, whether to report a message type as no-name-in-module, or E0611.
On by default.
</p>
</dd>
<dt><code>flycheck-pylintrc</code></dt>
<dd><a name="index-flycheck_002dpylintrc"></a>
<p>Configuration file for Pylint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<a name="R"></a><a name="R-1"></a>
<h3 class="unnumberedsec">R</h3>
<a name="index-Language_002c-R"></a>
<a name="index-R-language"></a>

<ul>
<li> <code>r-lintr</code> (syntax and style check with
<a href="https://github.com/jimhester/lintr">lintr</a>), with the following options:

<dl compact="compact">
<dt><code>flycheck-lintr-caching</code></dt>
<dd><a name="index-flycheck_002dlintr_002dcaching"></a>
<p>Whether to enable caching in lintr.  On by default.  Only disable it if
caching causes real problems.
</p>
</dd>
<dt><code>flycheck-lintr-linters</code></dt>
<dd><a name="index-flycheck_002dlintr_002dlinters"></a>
<p>Linters to use with lintr, as a string containing an R expression which
selects the linters to use.
</p></dd>
</dl>

</li></ul>

<a name="Racket"></a><a name="Racket-1"></a>
<h3 class="unnumberedsec">Racket</h3>
<a name="index-Language_002c-Racket"></a>
<a name="index-Racket-language"></a>

<ul>
<li> <code>racket</code> (syntax checker with <code>raco expand</code>, requires the
<code>compiler-lib</code> package)
</li></ul>

<a name="RPM-Spec"></a><a name="RPM-Spec-1"></a>
<h3 class="unnumberedsec">RPM Spec</h3>
<a name="index-Language_002c-RPM-Spec"></a>
<a name="index-RPM-Spec-language"></a>

<ul>
<li> <code>rpm-rpmlint</code>
(<a href="http://sourceforge.net/projects/rpmlint/">rpmlint</a>)
</li></ul>

<a name="reStructuredText"></a><a name="reStructuredText-1"></a>
<h3 class="unnumberedsec">reStructuredText</h3>
<a name="index-Language_002c-reStructuredText"></a>
<a name="index-reStructuredText-language"></a>

<ul>
<li> <code>rst-sphinx</code> (using <a href="http://sphinx-doc.org/">Sphinx</a>, for Sphinx
documentation files), or
<code>rst</code> (using <a href="http://docutils.sourceforge.net/">docutils</a>, for
plain reStructuredFiles files)
</li></ul>

<p><code>rst-sphinx</code> provides the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-sphinx-warn-on-missing-references</code></dt>
<dd><a name="index-flycheck_002dsphinx_002dwarn_002don_002dmissing_002dreferences"></a>
<p>Whether to emit warnings for all missing references in Sphinx.
</p></dd>
</dl>

<a name="Ruby"></a><a name="Ruby-1"></a>
<h3 class="unnumberedsec">Ruby</h3>
<a name="index-Language_002c-Ruby"></a>
<a name="index-Ruby-language"></a>

<ol>
<li> <code>ruby-rubocop</code> (syntax and style check using
<a href="http://batsov.com/rubocop/">RuboCop</a>)
</li><li> <code>ruby-rubylint</code> (syntax and style check using
<a href="http://code.yorickpeterse.com/ruby-lint/latest/">ruby-lint</a>)
</li></ol>

<p>These checkers provide the following options
</p>
<dl compact="compact">
<dt><code>flycheck-rubocop-lint-only</code></dt>
<dd><a name="index-flycheck_002drubocop_002dlint_002donly"></a>
<p>Whether to suppress warnings about style issues in Rubocop, via the
<samp>--lint</samp> option.
</p></dd>
<dt><code>flycheck-rubocoprc</code></dt>
<dd><a name="index-flycheck_002drubocoprc"></a>
<p>Configuration file for Rubocop.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
<dt><code>flycheck-rubylintrc</code></dt>
<dd><a name="index-flycheck_002drubylintrc"></a>
<p>Configuration file for ruby-lint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<p>If none of the above is available, Flycheck will fall back to one of the
following checkers for very basic checking:
</p>
<ul>
<li> <code>ruby</code> (using the <a href="https://www.ruby-lang.org/">standard Ruby
interpreter</a>), or
</li><li> <code>ruby-jruby</code> (using <a href="http://jruby.org/">JRuby</a>)
</li></ul>

<a name="Rust"></a><a name="Rust-1"></a>
<h3 class="unnumberedsec">Rust</h3>
<a name="index-Language_002c-Rust"></a>
<a name="index-Rust-language"></a>

<ul>
<li> <code>rust-cargo</code> (using the <a href="https://crates.io/">Cargo</a>), or

</li><li> <code>rust</code> (using the <a href="http://www.rust-lang.org/">Rust compiler</a>)

<p>These checkers provide the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-rust-args</code></dt>
<dd><a name="index-flycheck_002drust_002dargs"></a>
<p>A list of additional arguments for the Rust compiler <code>rustc</code>.
</p>
</dd>
<dt><code>flycheck-rust-check-tests</code></dt>
<dd><a name="index-flycheck_002drust_002dcheck_002dtests"></a>
<p>Whether to check test code in Rust.
</p>
</dd>
<dt><code>flycheck-rust-crate-root</code></dt>
<dd><a name="index-flycheck_002drust_002dcrate_002droot"></a>
<p>A path to the crate root for the current buffer, or nil if the current
buffer is a crate by itself.  <code>rust-cargo</code> ignores this option, as
the crate root comes from Cargo.
</p>
</dd>
<dt><code>flycheck-rust-crate-type</code></dt>
<dd><a name="index-flycheck_002drust_002dcrate_002dtype"></a>
<p>The type of the crate to check, as string for the
<samp>--crate-type</samp> option.
</p></dd>
<dt><code>flycheck-rust-library-path</code></dt>
<dd><a name="index-flycheck_002drust_002dlibrary_002dpath"></a>
<p>A list of additional library directories for Rust. Relative paths are
relative to the buffer being checked.
</p></dd>
</dl>

</li></ul>

<blockquote class="smallindentedblock">
<p>The <a href="https://github.com/flycheck/flycheck-rust">flycheck-rust</a> extension configures
Flycheck according to the current
<a href="http://doc.crates.io/guide.html">Cargo</a> project.
</p></blockquote>

<a name="Sass"></a><a name="Sass-1"></a>
<h3 class="unnumberedsec">Sass</h3>
<a name="index-Language_002c-Sass"></a>
<a name="index-Sass-language"></a>

<ul>
<li> <code>sass</code> (using the <a href="http://sass-lang.com/">standard Sass
processor</a>), with the following option:

<dl compact="compact">
<dt><code>flycheck-sass-compass</code></dt>
<dd><a name="index-flycheck_002dsass_002dcompass"></a>
<p>Whether to enable the Compass CSS framework in SASS, via
<samp>--compass</samp>.
</p></dd>
</dl>

</li></ul>

<a name="Scala"></a><a name="Scala-1"></a>
<h3 class="unnumberedsec">Scala</h3>
<a name="index-Language_002c-Scala"></a>
<a name="index-Scala-language"></a>

<ol>
<li> <code>scala</code> (syntax and type check using the
<a href="http://www.scala-lang.org/">Scala compiler</a>)
</li><li> <code>scala-scalastyle</code> (style check using
<a href="http://www.scalastyle.org/">Scalastyle</a>)
</li></ol>

<p>The <code>scala-scalastyle</code> syntax checker needs the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-scalastylerc</code></dt>
<dd><a name="index-flycheck_002dscalastylerc"></a>
<p>Configuration file for Scalastyle.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<p>If this option is not set, or if the configuration file was not found
<code>scala-scalastyle</code> will not be used.
</p>
<a name="SCSS"></a><a name="SCSS-1"></a>
<h3 class="unnumberedsec">SCSS</h3>
<a name="index-Language_002c-SCSS"></a>
<a name="index-SCSS-language"></a>

<ul>
<li> <code>scss-lint</code> (using <a href="https://github.com/brigade/scss-lint">SCSS-Lint</a>), or
</li><li> <code>scss</code> (using the <a href="http://sass-lang.com/">standard SCSS
processor</a>)
</li></ul>

<p>These syntax checkers provide the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-scss-compass</code></dt>
<dd><a name="index-flycheck_002dscss_002dcompass"></a>
<p>Whether to enable the Compass CSS framework in SCSS, via
<samp>--compass</samp>.
</p></dd>
<dt><code>flycheck-scss-lintrc</code></dt>
<dd><a name="index-flycheck_002dscss_002dlintrc"></a>
<p>Configuration file for SCSS-Lint.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<a name="Shell-scripting-languages"></a><a name="Shell-scripting-languages-1"></a>
<h3 class="unnumberedsec">Shell scripting languages</h3>
<a name="index-Language_002c-Shell-scripting-languages"></a>
<a name="index-Shell-scripting-languages-language"></a>

<ol>
<li> Syntax check with one of the following checkers, depending on the shell
used for the current Sh Mode buffer,
<ul>
<li> <code>sh-bash</code> (for <a href="http://www.gnu.org/software/bash/">Bash</a>)
</li><li> <code>sh-posix-dash</code> or <code>sh-posix-bash</code> (for POSIX shell scripts,
using <a href="http://gondor.apana.org.au/~herbert/dash/">Dash</a> or
<a href="http://www.gnu.org/software/bash/">Bash</a> respectively)
</li><li> <code>sh-zsh</code> (for <a href="http://www.zsh.org/">Zsh</a>)
</li></ul>
</li><li> <code>sh-shellcheck</code> (code and style check using
<a href="https://github.com/koalaman/shellcheck/">ShellCheck</a>)
</li></ol>

<p><code>sh-shellcheck</code> provides the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-shellcheck-excluded-warnings</code></dt>
<dd><a name="index-flycheck_002dshellcheck_002dexcluded_002dwarnings"></a>
<p>A list of excluded warnings for ShellCheck.
</p></dd>
</dl>

<a name="Slim"></a><a name="Slim-1"></a>
<h3 class="unnumberedsec">Slim</h3>
<a name="index-Language_002c-Slim"></a>
<a name="index-Slim-language"></a>

<ul>
<li> <code>slim</code> (using <a href="http://slim-lang.com/">Slim</a>)
</li></ul>

<a name="SQL"></a><a name="SQL-1"></a>
<h3 class="unnumberedsec">SQL</h3>
<a name="index-Language_002c-SQL"></a>
<a name="index-SQL-language"></a>

<ul>
<li> <code>sql-sqlint</code> (using <a href="https://github.com/purcell/sqlint">Sqlint</a>)
</li></ul>

<a name="TeX_002fLaTeX"></a><a name="TeX_002fLaTeX-1"></a>
<h3 class="unnumberedsec">TeX/LaTeX</h3>
<a name="index-Language_002c-TeX_002fLaTeX"></a>
<a name="index-TeX_002fLaTeX-language"></a>

<ul>
<li> <code>tex-chktex</code> (style check using
<a href="http://www.nongnu.org/chktex/">ChkTeX</a>), or
</li><li> <code>tex-lacheck</code> (style check using
<a href="http://www.ctan.org/pkg/lacheck">Lacheck</a>)
</li></ul>

<p><code>tex-chktex</code> provides the following option:
</p>
<dl compact="compact">
<dt><code>flycheck-chktexrc</code></dt>
<dd><a name="index-flycheck_002dchktexrc"></a>
<p>Configuration file for ChkTeX.  See <a href="#Syntax-checker-configuration-files">Syntax checker configuration files</a>, for more information about configuration files.
</p></dd>
</dl>

<a name="Texinfo"></a><a name="Texinfo-1"></a>
<h3 class="unnumberedsec">Texinfo</h3>
<a name="index-Language_002c-Texinfo"></a>
<a name="index-Texinfo-language"></a>

<ul>
<li> <code>texinfo</code> (using
<a href="http://www.gnu.org/software/texinfo/">makeinfo</a>)
</li></ul>

<a name="Verilog"></a><a name="Verilog-1"></a>
<h3 class="unnumberedsec">Verilog</h3>
<a name="index-Language_002c-Verilog"></a>
<a name="index-Verilog-language"></a>

<ul>
<li> <code>verilog-verilator</code> (using
<a href="http://www.veripool.org/wiki/verilator">Verilator</a>)
</li></ul>

<p><code>verilog-verilator</code> provides the following options:
</p>
<dl compact="compact">
<dt><code>flycheck-verilator-include-path</code></dt>
<dd><a name="index-flycheck_002dverilator_002dinclude_002dpath"></a>
<p>A list of include directories for Verilator.  Relative paths are relative to
the file being checked.
</p></dd>
</dl>

<a name="XML"></a><a name="XML-1"></a>
<h3 class="unnumberedsec">XML</h3>
<a name="index-Language_002c-XML"></a>
<a name="index-XML-language"></a>

<ul>
<li> <code>xml-xmlstarlet</code> (using <a href="http://xmlstar.sourceforge.net">XMLStarlet</a>),
or
</li><li> <code>xml-xmllint</code> (using <a href="http://www.xmlsoft.org/">xmllint</a>)
</li></ul>

<a name="YAML"></a><a name="YAML-1"></a>
<h3 class="unnumberedsec">YAML</h3>
<a name="index-Language_002c-YAML"></a>
<a name="index-YAML-language"></a>

<ul>
<li> <code>yaml-jsyaml</code> (using
<a href="https://github.com/nodeca/js-yaml">js-yaml</a>), or
</li><li> <code>yaml-ruby</code> (using Ruby&rsquo;s YAML parser)
</li></ul>


<hr>
<a name="Getting-Help"></a>
<div class="header">
<p>
Next: <a href="#GNU-Free-Documentation-License" accesskey="n" rel="next">GNU Free Documentation License</a>, Previous: <a href="#Supported-languages" accesskey="p" rel="prev">Supported languages</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Getting-Help-1"></a>
<h2 class="appendix">Appendix B Getting Help</h2>

<a name="Asking-questions"></a>
<h3 class="section">B.1 Asking questions</h3>

<p>Please ask questions about Flycheck on
<a href="https://emacs.stackexchange.com/questions/tagged/flycheck">Stack
Exchange</a> or in our <a href="https://gitter.im/flycheck/flycheck">Gitter
channel</a>.  We try to answer all questions as fast and as precise as
possible.
</p>
<a name="Reporting-issues"></a>
<h3 class="section">B.2 Reporting issues</h3>
<a name="Issues"></a>
<p>To report problems or bugs, please use our
<a href="https://github.com/flycheck/flycheck/issues">issue tracker</a>.  Our
<a href="https://github.com/flycheck/flycheck/blob/master/CONTRIBUTING.md">Contribution
Guidelines</a> help you to create good bug reports; please take a look.
</p>
<p>We welcome patches and pull requests that fix bugs or provide new
features.  Please read our Contribution Guidelines for help and
guidelines before submitting pull requests.  When making larger changes
to Flycheck or implementing new features we recommend that you first
open a separate issue or ask in our Gitter channel to discuss
you intended changes.
</p>
<a name="Conduct"></a>
<h3 class="section">B.3 Conduct</h3>

<p>Please follow our <a href="http://www.flycheck.org/conduct.html">Code of Conduct</a> in all our
communication channels.
</p>
<hr>
<a name="GNU-Free-Documentation-License"></a>
<div class="header">
<p>
Next: <a href="#Main-Index" accesskey="n" rel="next">Main Index</a>, Previous: <a href="#Getting-Help" accesskey="p" rel="prev">Getting Help</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="GNU-Free-Documentation-License-1"></a>
<h2 class="appendix">Appendix C GNU Free Documentation License</h2>

<div align="center">Version 1.3, 3 November 2008
</div>

<div class="display">
<pre class="display">Copyright &copy; 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
<a href="http://fsf.org/">http://fsf.org/</a>

Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
</pre></div>

<ol>
<li> PREAMBLE

<p>The purpose of this License is to make a manual, textbook, or other
functional and useful document <em>free</em> in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.
</p>
<p>This License is a kind of &ldquo;copyleft&rdquo;, which means that derivative
works of the document must themselves be free in the same sense.  It
complements the GNU General Public License, which is a copyleft
license designed for free software.
</p>
<p>We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does.  But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book.  We recommend this License
principally for works whose purpose is instruction or reference.
</p>
</li><li> APPLICABILITY AND DEFINITIONS

<p>This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License.  Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein.  The &ldquo;Document&rdquo;, below,
refers to any such manual or work.  Any member of the public is a
licensee, and is addressed as &ldquo;you&rdquo;.  You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.
</p>
<p>A &ldquo;Modified Version&rdquo; of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
</p>
<p>A &ldquo;Secondary Section&rdquo; is a named appendix or a front-matter section
of the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document&rsquo;s overall
subject (or to related matters) and contains nothing that could fall
directly within that overall subject.  (Thus, if the Document is in
part a textbook of mathematics, a Secondary Section may not explain
any mathematics.)  The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding
them.
</p>
<p>The &ldquo;Invariant Sections&rdquo; are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License.  If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant.  The Document may contain zero
Invariant Sections.  If the Document does not identify any Invariant
Sections then there are none.
</p>
<p>The &ldquo;Cover Texts&rdquo; are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License.  A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.
</p>
<p>A &ldquo;Transparent&rdquo; copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters.  A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text.  A copy that is not &ldquo;Transparent&rdquo; is called &ldquo;Opaque&rdquo;.
</p>
<p>Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input
format, SGML or XML using a publicly available
DTD, and standard-conforming simple HTML,
PostScript or PDF designed for human modification.  Examples
of transparent image formats include PNG, XCF and
JPG.  Opaque formats include proprietary formats that can be
read and edited only by proprietary word processors, SGML or
XML for which the DTD and/or processing tools are
not generally available, and the machine-generated HTML,
PostScript or PDF produced by some word processors for
output purposes only.
</p>
<p>The &ldquo;Title Page&rdquo; means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page.  For works in
formats which do not have any title page as such, &ldquo;Title Page&rdquo; means
the text near the most prominent appearance of the work&rsquo;s title,
preceding the beginning of the body of the text.
</p>
<p>The &ldquo;publisher&rdquo; means any person or entity that distributes copies
of the Document to the public.
</p>
<p>A section &ldquo;Entitled XYZ&rdquo; means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language.  (Here XYZ stands for a
specific section name mentioned below, such as &ldquo;Acknowledgements&rdquo;,
&ldquo;Dedications&rdquo;, &ldquo;Endorsements&rdquo;, or &ldquo;History&rdquo;.)  To &ldquo;Preserve the Title&rdquo;
of such a section when you modify the Document means that it remains a
section &ldquo;Entitled XYZ&rdquo; according to this definition.
</p>
<p>The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document.  These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.
</p>
</li><li> VERBATIM COPYING

<p>You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License.  You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute.  However, you may accept
compensation in exchange for copies.  If you distribute a large enough
number of copies you must also follow the conditions in section 3.
</p>
<p>You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
</p>
</li><li> COPYING IN QUANTITY

<p>If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document&rsquo;s license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover.  Both covers must also clearly and legibly identify
you as the publisher of these copies.  The front cover must present
the full title with all words of the title equally prominent and
visible.  You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.
</p>
<p>If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
</p>
<p>If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.
</p>
<p>It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
</p>
</li><li> MODIFICATIONS

<p>You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it.  In addition, you must do these things in the Modified Version:
</p>
<ol>
<li> Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document).  You may use the same title as a previous version
if the original publisher of that version gives permission.

</li><li> List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.

</li><li> State on the Title page the name of the publisher of the
Modified Version, as the publisher.

</li><li> Preserve all the copyright notices of the Document.

</li><li> Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.

</li><li> Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.

</li><li> Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document&rsquo;s license notice.

</li><li> Include an unaltered copy of this License.

</li><li> Preserve the section Entitled &ldquo;History&rdquo;, Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page.  If
there is no section Entitled &ldquo;History&rdquo; in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.

</li><li> Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on.  These may be placed in the &ldquo;History&rdquo; section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.

</li><li> For any section Entitled &ldquo;Acknowledgements&rdquo; or &ldquo;Dedications&rdquo;, Preserve
the Title of the section, and preserve in the section all the
substance and tone of each of the contributor acknowledgements and/or
dedications given therein.

</li><li> Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles.  Section numbers
or the equivalent are not considered part of the section titles.

</li><li> Delete any section Entitled &ldquo;Endorsements&rdquo;.  Such a section
may not be included in the Modified Version.

</li><li> Do not retitle any existing section to be Entitled &ldquo;Endorsements&rdquo; or
to conflict in title with any Invariant Section.

</li><li> Preserve any Warranty Disclaimers.
</li></ol>

<p>If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant.  To do this, add their titles to the
list of Invariant Sections in the Modified Version&rsquo;s license notice.
These titles must be distinct from any other section titles.
</p>
<p>You may add a section Entitled &ldquo;Endorsements&rdquo;, provided it contains
nothing but endorsements of your Modified Version by various
parties&mdash;for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
</p>
<p>You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version.  Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity.  If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
</p>
<p>The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
</p>
</li><li> COMBINING DOCUMENTS

<p>You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.
</p>
<p>The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy.  If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.
</p>
<p>In the combination, you must combine any sections Entitled &ldquo;History&rdquo;
in the various original documents, forming one section Entitled
&ldquo;History&rdquo;; likewise combine any sections Entitled &ldquo;Acknowledgements&rdquo;,
and any sections Entitled &ldquo;Dedications&rdquo;.  You must delete all
sections Entitled &ldquo;Endorsements.&rdquo;
</p>
</li><li> COLLECTIONS OF DOCUMENTS

<p>You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
</p>
<p>You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
</p>
</li><li> AGGREGATION WITH INDEPENDENT WORKS

<p>A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an &ldquo;aggregate&rdquo; if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation&rsquo;s users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.
</p>
<p>If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document&rsquo;s Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole
aggregate.
</p>
</li><li> TRANSLATION

<p>Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections.  You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers.  In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.
</p>
<p>If a section in the Document is Entitled &ldquo;Acknowledgements&rdquo;,
&ldquo;Dedications&rdquo;, or &ldquo;History&rdquo;, the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual
title.
</p>
</li><li> TERMINATION

<p>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided under this License.  Any attempt
otherwise to copy, modify, sublicense, or distribute it is void, and
will automatically terminate your rights under this License.
</p>
<p>However, if you cease all violation of this License, then your license
from a particular copyright holder is reinstated (a) provisionally,
unless and until the copyright holder explicitly and finally
terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to
60 days after the cessation.
</p>
<p>Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
</p>
<p>Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License.  If your rights have been terminated and not permanently
reinstated, receipt of a copy of some or all of the same material does
not give you any rights to use it.
</p>
</li><li> FUTURE REVISIONS OF THIS LICENSE

<p>The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time.  Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.  See
<a href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.
</p>
<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License &ldquo;or any later version&rdquo; applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation.  If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.  If the Document
specifies that a proxy can decide which future versions of this
License can be used, that proxy&rsquo;s public statement of acceptance of a
version permanently authorizes you to choose that version for the
Document.
</p>
</li><li> RELICENSING

<p>&ldquo;Massive Multiauthor Collaboration Site&rdquo; (or &ldquo;MMC Site&rdquo;) means any
World Wide Web server that publishes copyrightable works and also
provides prominent facilities for anybody to edit those works.  A
public wiki that anybody can edit is an example of such a server.  A
&ldquo;Massive Multiauthor Collaboration&rdquo; (or &ldquo;MMC&rdquo;) contained in the
site means any set of copyrightable works thus published on the MMC
site.
</p>
<p>&ldquo;CC-BY-SA&rdquo; means the Creative Commons Attribution-Share Alike 3.0
license published by Creative Commons Corporation, a not-for-profit
corporation with a principal place of business in San Francisco,
California, as well as future copyleft versions of that license
published by that same organization.
</p>
<p>&ldquo;Incorporate&rdquo; means to publish or republish a Document, in whole or
in part, as part of another Document.
</p>
<p>An MMC is &ldquo;eligible for relicensing&rdquo; if it is licensed under this
License, and if all works that were first published under this License
somewhere other than this MMC, and subsequently incorporated in whole
or in part into the MMC, (1) had no cover texts or invariant sections,
and (2) were thus incorporated prior to November 1, 2008.
</p>
<p>The operator of an MMC Site may republish an MMC contained in the site
under CC-BY-SA on the same site at any time before August 1, 2009,
provided the MMC is eligible for relicensing.
</p>
</li></ol>

<a name="ADDENDUM_003a-How-to-use-this-License-for-your-documents"></a>
<h3 class="heading">ADDENDUM: How to use this License for your documents</h3>

<p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:
</p>
<div class="smallexample">
<pre class="smallexample">  Copyright (C)  <var>year</var>  <var>your name</var>.
  Permission is granted to copy, distribute and/or modify this document
  under the terms of the GNU Free Documentation License, Version 1.3
  or any later version published by the Free Software Foundation;
  with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
  Texts.  A copy of the license is included in the section entitled ``GNU
  Free Documentation License''.
</pre></div>

<p>If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the &ldquo;with&hellip;Texts.&rdquo; line with this:
</p>
<div class="smallexample">
<pre class="smallexample">    with the Invariant Sections being <var>list their titles</var>, with
    the Front-Cover Texts being <var>list</var>, and with the Back-Cover Texts
    being <var>list</var>.
</pre></div>

<p>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.
</p>
<p>If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.
</p>

<hr>
<a name="Main-Index"></a>
<div class="header">
<p>
Next: <a href="#Key-Index" accesskey="n" rel="next">Key Index</a>, Previous: <a href="#GNU-Free-Documentation-License" accesskey="p" rel="prev">GNU Free Documentation License</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Main-Index-1"></a>
<h2 class="unnumbered">Main Index</h2>

<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Main-Index_cp_letter-A"><b>A</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-C"><b>C</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-D"><b>D</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-E"><b>E</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-F"><b>F</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-G"><b>G</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-H"><b>H</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-I"><b>I</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-J"><b>J</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-L"><b>L</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-M"><b>M</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-O"><b>O</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-P"><b>P</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-R"><b>R</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-S"><b>S</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-T"><b>T</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-V"><b>V</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-W"><b>W</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-X"><b>X</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-Y"><b>Y</b></a>
 &nbsp; 
</td></tr></table>
<table class="index-cp" border="0">
<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> Section</th></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-A">A</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Ada-language">Ada language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-AsciiDoc-language">AsciiDoc language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-automatic-syntax-checker-selection">automatic syntax checker selection</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-C">C</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002fC_002b_002b-language">C/C++ language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-CFEngine-language">CFEngine language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-chaining-of-syntax-checkers">chaining of syntax checkers</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Chef-language">Chef language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Coffeescript-language">Coffeescript language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-configuration-files-of-syntax-checkers">configuration files of syntax checkers</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Coq-language">Coq language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-CSS-language">CSS language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-D">D</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-D-language">D language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-E">E</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Emacs-Lisp-language">Emacs Lisp language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Erlang-language">Erlang language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-error-display-function">error display function</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-error-tooltip">error tooltip</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-ERuby-language">ERuby language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-executables-of-syntax-checkers">executables of syntax checkers</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-F">F</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-features">features</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Introduction">Introduction</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck-mode">flycheck mode</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Fortran-language">Fortran language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-functions-for-error-display">functions for error display</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-G">G</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Go-language">Go language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Groovy-language">Groovy language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-H">H</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Haml-language">Haml language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Handlebars-language">Handlebars language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Haskell-language">Haskell language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-HTML-language">HTML language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-I">I</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-installation">installation</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Installation">Installation</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-J">J</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Jade-language">Jade language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Javascript-language">Javascript language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-JSON-language">JSON language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-L">L</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Ada">Language, Ada</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-AsciiDoc">Language, AsciiDoc</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-C_002fC_002b_002b">Language, C/C++</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-CFEngine">Language, CFEngine</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Chef">Language, Chef</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Coffeescript">Language, Coffeescript</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Coq">Language, Coq</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-CSS">Language, CSS</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-D">Language, D</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Emacs-Lisp">Language, Emacs Lisp</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Erlang">Language, Erlang</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-ERuby">Language, ERuby</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Fortran">Language, Fortran</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Go">Language, Go</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Groovy">Language, Groovy</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Haml">Language, Haml</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Handlebars">Language, Handlebars</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Haskell">Language, Haskell</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-HTML">Language, HTML</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Jade">Language, Jade</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Javascript">Language, Javascript</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-JSON">Language, JSON</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Less">Language, Less</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Lua">Language, Lua</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Perl">Language, Perl</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-PHP">Language, PHP</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Processing">Language, Processing</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Puppet">Language, Puppet</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Python">Language, Python</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-R">Language, R</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Racket">Language, Racket</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-reStructuredText">Language, reStructuredText</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-RPM-Spec">Language, RPM Spec</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Ruby">Language, Ruby</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Rust">Language, Rust</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Sass">Language, Sass</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Scala">Language, Scala</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-SCSS">Language, SCSS</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Shell-scripting-languages">Language, Shell scripting languages</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Slim">Language, Slim</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-SQL">Language, SQL</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-TeX_002fLaTeX">Language, TeX/LaTeX</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Texinfo">Language, Texinfo</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-Verilog">Language, Verilog</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-XML">Language, XML</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Language_002c-YAML">Language, YAML</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Less-language">Less language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Lua-language">Lua language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-M">M</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-manual-syntax-checker-selection">manual syntax checker selection</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-O">O</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-operating-system">operating system</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Installation">Installation</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-options-of-syntax-checkers">options of syntax checkers</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-P">P</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Perl-language">Perl language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-PHP-language">PHP language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-prerequisites">prerequisites</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Installation">Installation</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Processing-language">Processing language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Puppet-language">Puppet language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Python-language">Python language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-R">R</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-R-language">R language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Racket-language">Racket language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-reStructuredText-language">reStructuredText language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-RPM-Spec-language">RPM Spec language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Ruby-language">Ruby language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Rust-language">Rust language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-S">S</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Sass-language">Sass language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Scala-language">Scala language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-SCSS-language">SCSS language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Shell-scripting-languages-language">Shell scripting languages language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Slim-language">Slim language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-SQL-language">SQL language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker">syntax checker</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker-configuration-files">syntax checker configuration files</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker-executables">syntax checker executables</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker-options">syntax checker options</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker-selection_002c-automatic">syntax checker selection, automatic</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-syntax-checker-selection_002c-manual">syntax checker selection, manual</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-T">T</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-TeX_002fLaTeX-language">TeX/LaTeX language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-Texinfo-language">Texinfo language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-V">V</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Verilog-language">Verilog language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-W">W</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-Windows">Windows</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Installation">Installation</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-X">X</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-XML-language">XML language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Main-Index_cp_letter-Y">Y</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-YAML-language">YAML language</a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
</table>
<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Main-Index_cp_letter-A"><b>A</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-C"><b>C</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-D"><b>D</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-E"><b>E</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-F"><b>F</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-G"><b>G</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-H"><b>H</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-I"><b>I</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-J"><b>J</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-L"><b>L</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-M"><b>M</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-O"><b>O</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-P"><b>P</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-R"><b>R</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-S"><b>S</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-T"><b>T</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-V"><b>V</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-W"><b>W</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-X"><b>X</b></a>
 &nbsp; 
<a class="summary-letter" href="#Main-Index_cp_letter-Y"><b>Y</b></a>
 &nbsp; 
</td></tr></table>

<hr>
<a name="Key-Index"></a>
<div class="header">
<p>
Next: <a href="#Function-and-Variable-Index" accesskey="n" rel="next">Function and Variable Index</a>, Previous: <a href="#Main-Index" accesskey="p" rel="prev">Main Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Key-Index-1"></a>
<h2 class="unnumbered">Key Index</h2>

<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Key-Index_ky_letter-C"><b>C</b></a>
 &nbsp; 
<a class="summary-letter" href="#Key-Index_ky_letter-M"><b>M</b></a>
 &nbsp; 
</td></tr></table>
<table class="index-ky" border="0">
<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> Section</th></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Key-Index_ky_letter-C">C</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-_003f"><code>C-c ! ?</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-c"><code>C-c ! c</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-C_002dc"><code>C-c ! C-c</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Finding-error-patterns">Finding error patterns</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-C_002dw"><code>C-c ! C-w</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Killing-errors">Killing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-e"><code>C-c ! e</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-h"><code>C-c ! h</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-l"><code>C-c ! l</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-n"><code>C-c ! n</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-p"><code>C-c ! p</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-s"><code>C-c ! s</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-v"><code>C-c ! v</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dc-_0021-x"><code>C-c ! x</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002dh-_002e"><code>C-h .</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002du-C_002dc-_0021-C_002dw"><code>C-u C-c ! C-w</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Killing-errors">Killing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002du-C_002dc-_0021-e"><code>C-u C-c ! e</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002du-C_002dc-_0021-s"><code>C-u C-c ! s</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-C_002du-C_002dc-_0021-x"><code>C-u C-c ! x</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Key-Index_ky_letter-M">M</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-M_002d0-C_002dc-_0021-C_002dw"><code>M-0 C-c ! C-w</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Killing-errors">Killing errors</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
</table>
<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Key-Index_ky_letter-C"><b>C</b></a>
 &nbsp; 
<a class="summary-letter" href="#Key-Index_ky_letter-M"><b>M</b></a>
 &nbsp; 
</td></tr></table>

<hr>
<a name="Function-and-Variable-Index"></a>
<div class="header">
<p>
Previous: <a href="#Key-Index" accesskey="p" rel="prev">Key Index</a>, Up: <a href="#Top" accesskey="u" rel="up">Top</a> &nbsp; [<a href="#Main-Index" title="Index" rel="index">Index</a>]</p>
</div>
<a name="Function-and-variable-index"></a>
<h2 class="unnumbered">Function and variable index</h2>

<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-D"><b>D</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-F"><b>F</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-G"><b>G</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-L"><b>L</b></a>
 &nbsp; 
</td></tr></table>
<table class="index-fn" border="0">
<tr><td></td><th align="left">Index Entry</th><td>&nbsp;</td><th align="left"> Section</th></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Function-and-Variable-Index_fn_letter-D">D</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-display_002dlocal_002dhelp"><code>display-local-help</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Function-and-Variable-Index_fn_letter-F">F</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dbuffer"><code>flycheck-buffer</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcheck_002dsyntax_002dautomatically"><code>flycheck-check-syntax-automatically</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dchecker"><code>flycheck-checker</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dchecker_002derror_002dthreshold"><code>flycheck-checker-error-threshold</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcheckers"><code>flycheck-checkers</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dchktexrc"><code>flycheck-chktexrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dargs"><code>flycheck-clang-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dblocks"><code>flycheck-clang-blocks</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002ddefinitions"><code>flycheck-clang-definitions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dinclude_002dpath"><code>flycheck-clang-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dincludes"><code>flycheck-clang-includes</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dlanguage_002dstandard"><code>flycheck-clang-language-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dms_002dextensions"><code>flycheck-clang-ms-extensions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dno_002dexceptions"><code>flycheck-clang-no-exceptions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dno_002drtti"><code>flycheck-clang-no-rtti</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dpedantic"><code>flycheck-clang-pedantic</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dpedantic_002derrors"><code>flycheck-clang-pedantic-errors</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dstandard_002dlibrary"><code>flycheck-clang-standard-library</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclang_002dwarnings"><code>flycheck-clang-warnings</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dclear"><code>flycheck-clear</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcoffeelintrc"><code>flycheck-coffeelintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcompile"><code>flycheck-compile</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Finding-error-patterns">Finding error patterns</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcopy_002derrors_002das_002dkill"><code>flycheck-copy-errors-as-kill</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Killing-errors">Killing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcppcheck_002dchecks"><code>flycheck-cppcheck-checks</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcppcheck_002dinclude_002dpath"><code>flycheck-cppcheck-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcppcheck_002dinconclusive"><code>flycheck-cppcheck-inconclusive</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dcppcheck_002dlanguage_002dstandard"><code>flycheck-cppcheck-language-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddescribe_002dchecker"><code>flycheck-describe-checker</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisable_002dchecker"><code>flycheck-disable-checker</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisabled_002dcheckers"><code>flycheck-disabled-checkers</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisplay_002derror_002dat_002dpoint"><code>flycheck-display-error-at-point</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisplay_002derror_002dmessages"><code>flycheck-display-error-messages</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisplay_002derror_002dmessages_002dunless_002derror_002dlist"><code>flycheck-display-error-messages-unless-error-list</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisplay_002derrors_002ddelay"><code>flycheck-display-errors-delay</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddisplay_002derrors_002dfunction"><code>flycheck-display-errors-function</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddmd_002dargs"><code>flycheck-dmd-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002ddmd_002dinclude_002dpath"><code>flycheck-dmd-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002demacs_002dlisp_002dinitialize_002dpackages"><code>flycheck-emacs-lisp-initialize-packages</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002demacs_002dlisp_002dload_002dpath"><code>flycheck-emacs-lisp-load-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002demacs_002dlisp_002dpackage_002duser_002ddir"><code>flycheck-emacs-lisp-package-user-dir</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derlang_002dinclude_002dpath"><code>flycheck-erlang-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derlang_002dlibrary_002dpath"><code>flycheck-erlang-library-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derror"><code>flycheck-error</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derror_002dlist_002dafter_002drefresh_002dhook"><code>flycheck-error-list-after-refresh-hook</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derror_002dlist_002dhighlight"><code>flycheck-error-list-highlight</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002derror_002dlist_002dminimum_002dlevel"><code>flycheck-error-list-minimum-level</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002deslint_002drulesdir"><code>flycheck-eslint-rulesdir</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002deslintrc"><code>flycheck-eslintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dfirst_002derror"><code>flycheck-first-error</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dflake8_002derror_002dlevel_002dalist"><code>flycheck-flake8-error-level-alist</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dflake8_002dmaximum_002dcomplexity"><code>flycheck-flake8-maximum-complexity</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dflake8_002dmaximum_002dline_002dlength"><code>flycheck-flake8-maximum-line-length</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dflake8rc"><code>flycheck-flake8rc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dfoodcritic_002dtags"><code>flycheck-foodcritic-tags</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dargs"><code>flycheck-gcc-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002ddefinitions"><code>flycheck-gcc-definitions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dinclude_002dpath"><code>flycheck-gcc-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dincludes"><code>flycheck-gcc-includes</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dlanguage_002dstandard"><code>flycheck-gcc-language-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dno_002dexceptions"><code>flycheck-gcc-no-exceptions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dno_002drtti"><code>flycheck-gcc-no-rtti</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dopenmp"><code>flycheck-gcc-openmp</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dpedantic"><code>flycheck-gcc-pedantic</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dpedantic_002derrors"><code>flycheck-gcc-pedantic-errors</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgcc_002dwarnings"><code>flycheck-gcc-warnings</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgfortran_002dargs"><code>flycheck-gfortran-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgfortran_002dinclude_002dpath"><code>flycheck-gfortran-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgfortran_002dlanguage_002dstandard"><code>flycheck-gfortran-language-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgfortran_002dlayout"><code>flycheck-gfortran-layout</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgfortran_002dwarnings"><code>flycheck-gfortran-warnings</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dghc_002dargs"><code>flycheck-ghc-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dghc_002dlanguage_002dextensions"><code>flycheck-ghc-language-extensions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dghc_002dno_002duser_002dpackage_002ddatabase"><code>flycheck-ghc-no-user-package-database</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dghc_002dpackage_002ddatabases"><code>flycheck-ghc-package-databases</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dghc_002dsearch_002dpath"><code>flycheck-ghc-search-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgjslintrc"><code>flycheck-gjslintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dglobal_002dmodes"><code>flycheck-global-modes</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgnat_002dargs"><code>flycheck-gnat-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgnat_002dinclude_002dpath"><code>flycheck-gnat-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgnat_002dlanguage_002dstandard"><code>flycheck-gnat-language-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgnat_002dwarnings"><code>flycheck-gnat-warnings</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgo_002dbuild_002dinstall_002ddeps"><code>flycheck-go-build-install-deps</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgo_002dbuild_002dtags"><code>flycheck-go-build-tags</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgo_002dvet_002dprint_002dfunctions"><code>flycheck-go-vet-print-functions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dgo_002dvet_002dshadow"><code>flycheck-go-vet-shadow</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhelp_002decho_002dfunction"><code>flycheck-help-echo-function</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Displaying-errors">Displaying errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhighlighting_002dmode"><code>flycheck-highlighting-mode</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhlint_002dargs"><code>flycheck-hlint-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhlint_002dhint_002dpackages"><code>flycheck-hlint-hint-packages</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhlint_002dignore_002drules"><code>flycheck-hlint-ignore-rules</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhlint_002dlanguage_002dextensions"><code>flycheck-hlint-language-extensions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dhlintrc"><code>flycheck-hlintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002didle_002dchange_002ddelay"><code>flycheck-idle-change-delay</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dindication_002dmode"><code>flycheck-indication-mode</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dinfo"><code>flycheck-info</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002djscsrc"><code>flycheck-jscsrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002djshint_002dextract_002djavascript"><code>flycheck-jshint-extract-javascript</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002djshintrc"><code>flycheck-jshintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dkeymap_002dprefix"><code>flycheck-keymap-prefix</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Usage">Usage</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dlintr_002dcaching"><code>flycheck-lintr-caching</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dlintr_002dlinters"><code>flycheck-lintr-linters</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dlist_002derrors"><code>flycheck-list-errors</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dlocate_002dconfig_002dfile_002dfunctions"><code>flycheck-locate-config-file-functions</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dluacheckrc"><code>flycheck-luacheckrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dmode"><code>flycheck-mode</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dnavigation_002dminimum_002dlevel"><code>flycheck-navigation-minimum-level</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dnext_002derror"><code>flycheck-next-error</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dperl_002dinclude_002dpath"><code>flycheck-perl-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dperlcritic_002dseverity"><code>flycheck-perlcritic-severity</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dperlcriticrc"><code>flycheck-perlcriticrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dphpcs_002dstandard"><code>flycheck-phpcs-standard</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dphpmd_002drulesets"><code>flycheck-phpmd-rulesets</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dprevious_002derror"><code>flycheck-previous-error</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dpuppet_002dlint_002ddisabled_002dchecks"><code>flycheck-puppet-lint-disabled-checks</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dpuppet_002dlint_002drc"><code>flycheck-puppet-lint-rc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dpylint_002duse_002dsymbolic_002did"><code>flycheck-pylint-use-symbolic-id</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dpylintrc"><code>flycheck-pylintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drubocop_002dlint_002donly"><code>flycheck-rubocop-lint-only</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drubocoprc"><code>flycheck-rubocoprc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drubylintrc"><code>flycheck-rubylintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drust_002dargs"><code>flycheck-rust-args</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drust_002dcheck_002dtests"><code>flycheck-rust-check-tests</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drust_002dcrate_002droot"><code>flycheck-rust-crate-root</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drust_002dcrate_002dtype"><code>flycheck-rust-crate-type</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002drust_002dlibrary_002dpath"><code>flycheck-rust-library-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dsass_002dcompass"><code>flycheck-sass-compass</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dscalastylerc"><code>flycheck-scalastylerc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dscss_002dcompass"><code>flycheck-scss-compass</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dscss_002dlintrc"><code>flycheck-scss-lintrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dselect_002dchecker"><code>flycheck-select-checker</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Syntax-checkers">Syntax checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dset_002dchecker_002dexecutable"><code>flycheck-set-checker-executable</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Configuring-checkers">Configuring checkers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dshellcheck_002dexcluded_002dwarnings"><code>flycheck-shellcheck-excluded-warnings</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dsphinx_002dwarn_002don_002dmissing_002dreferences"><code>flycheck-sphinx-warn-on-missing-references</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dstandard_002derror_002dnavigation"><code>flycheck-standard-error-navigation</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Navigating-errors">Navigating errors</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dtemp_002dprefix"><code>flycheck-temp-prefix</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dtidyrc"><code>flycheck-tidyrc</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dverify_002dsetup"><code>flycheck-verify-setup</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dverilator_002dinclude_002dpath"><code>flycheck-verilator-include-path</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Supported-languages">Supported languages</a></td></tr>
<tr><td></td><td valign="top"><a href="#index-flycheck_002dwarning"><code>flycheck-warning</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Reporting-results">Reporting results</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Function-and-Variable-Index_fn_letter-G">G</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-global_002dflycheck_002dmode"><code>global-flycheck-mode</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Checking-buffers">Checking buffers</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Function-and-Variable-Index_fn_letter-L">L</a></th><td></td><td></td></tr>
<tr><td></td><td valign="top"><a href="#index-list_002dflycheck_002derrors"><code>list-flycheck-errors</code></a>:</td><td>&nbsp;</td><td valign="top"><a href="#Listing-errors">Listing errors</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
</table>
<table><tr><th valign="top">Jump to: &nbsp; </th><td><a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-D"><b>D</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-F"><b>F</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-G"><b>G</b></a>
 &nbsp; 
<a class="summary-letter" href="#Function-and-Variable-Index_fn_letter-L"><b>L</b></a>
 &nbsp; 
</td></tr></table>

<hr>



</body>
</html>