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

README: more details about enabling checkers.

Browse Source
This commit is contained in:
LCD 47 2015-02-22 19:03:44 +02:00
parent bccfdea4e8
commit 71aa71bc1b
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.markdown
View File

@ -184,6 +184,14 @@ supported, look at the [wiki][3]. Note that aliases do not work; the actual
executables must be available in your `$PATH`. Symbolic links are okay though.
You can see syntastic's idea of available checkers by running `:SyntasticInfo`.
A second reason is that the checker you want to run might not be enabled,
even though it is available. Syntastic comes preconfigured with a default
list of enabled checkers per filetype, but this list is deliberatley kept
short in order to prevent slowing down Vim or trying to run conflicting
checkers. The same command `:SyntasticInfo` will also show you which checkers
are enabled. You can tell syntastic which checkers you want to run by setting
`g:syntastic_<filetype>_checkers` in your `vimrc` (see [below](#faqcheckers)).
Another reason it could fail is that either the command line options or the
error output for a 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

2
plugin/syntastic.vim
View File

@ -19,7 +19,7 @@ if has('reltime')
lockvar! g:_SYNTASTIC_START
endif
let g:_SYNTASTIC_VERSION = '3.6.0-33'
let g:_SYNTASTIC_VERSION = '3.6.0-34'
lockvar g:_SYNTASTIC_VERSION
" Sanity checks {{{1