vim/syntastic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

add an faq RE setting which checkers to use

Browse Source
This commit is contained in:
Martin Grenfell 2013-02-10 16:51:02 +00:00
parent 6acff371af
commit 240ad4b34f
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.markdown
View File

@ -105,6 +105,26 @@ A. The most likely reason is that the syntax checker that it requires isn't inst
Another reason it could fail is that the error output for the syntax checker may have changed. In this case, make sure you have the latest version of the syntax checker installed. If it still fails then create an issue - or better yet, create a pull request.
__Q. Syntastic supports several checkers for my filetype - how do I tell it which one(s) to use?__
A. Stick a line like this in your vimrc:
`let g:syntastic_<filetype>_checkers=['<checker-name>']`
To see the list of checkers for your filetype, look in `syntax_checkers/<filetype>/`.
e.g. Python has the following checkers: `flake8`, `pyflakes`, `pylint` and a native `python` checker.
To tell syntastic to use `pylint`, you would use this setting:
`let g:syntastic_python_checkers=['pylint']`
Some filetypes, like PHP, have style checkers as well as syntax checkers. These can be chained together like this:
`let g:syntastic_php_checkers=['php', 'phpcs', 'phpmd']`
This is telling syntastic to run the `php` checker first, and if no errors are found, run `phpcs`, and then `phpmd`.
__Q. How can I jump between the different errors without using the location list at the bottom of the window?__
A. Vim provides several built in commands for this. See `:help :lnext` and `:help :lprev`.