Flycheck 0.17 was released today. Though it’s just about two weeks since the last release, there are quite some changes.
Table of Contents
The default value of flycheck-completion-system was changed to nil, i.e. Flycheck now uses plain completing-read as default completion system. To restore the previous default (i.e. IDO), customize it with M-x customize-variable RET flycheck-completion-system or add the following to your init.el:
(eval-after-load 'flycheck '(setq flycheck-completion-system 'ido))
Also, flycheck-count-errors was changed to count errors of all levels. It returns an alist mapping error levels to the amount of errors of that level.
The new manual is written with Sphinx instead of Texinfo. The underlying markup is ReStructuredText, which is simpler, less cluttered, and more powerful than the TeX dialect of Texinfo. It is also more popular, as nowadays Sphinx has become a standard tool among Python developers, and is also increasingly used with other languages as well. For instance, the LLVM documentation is written in Sphinx.
Besides providing a better HTML documentation, we hope that the new manual lowers the barrier to external contributors and increases the amount of contributions to the documentation.
The documentation is now automatically re-build after each push to the Github repository, so that http://flycheck.readthedocs.org/en/latest now always hosts the up to date documentation. Besides, there are separate sites for each versioned release of Flycheck. For instance, http://flycheck.readthedocs.org/en/0.17 now hosts the documentation of Flycheck 0.17 now.
Beyond the manual itself, the new documentation now also includes the release notes, which were previously hosted at http://lunaryorn.com, and the comparison with Flymake, which was previously hosted at the Github Wiki of Flycheck. The Github Wiki is disabled now, to make all documentation available from a single place.
Unfortunately, the Info manual included in the Flycheck ELPA packages is somewhat inferior now, because there is some idiomatic gap between Sphinx and Texinfo. It’s still usable, though, and we hope to overcome the most striking shortcomings over the time.
The rust syntax checker now uses --no-trans to check for more than just syntax errors. For instance, it will report unused variables now.
As part of the transition to the new manual, Flycheck now provides a syntax checker for Sphinx documents (rst-sphinx). The rst syntax checker does not check documents within a Sphinx project anymore, do avoid false positives from Sphinx-specific markup.