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

README: rephrase.

Browse Source
This commit is contained in:
LCD 47 2015-02-23 09:06:01 +02:00
parent 71aa71bc1b
commit f4b064e2de
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.markdown
View File

@ -184,18 +184,18 @@ 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. executables must be available in your `$PATH`. Symbolic links are okay though.
You can see syntastic's idea of available checkers by running `:SyntasticInfo`. 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, A second probable reason is that none of the available checkers are
even though it is available. Syntastic comes preconfigured with a default enabled. Syntastic comes preconfigured with a default list of enabled checkers
list of enabled checkers per filetype, but this list is deliberatley kept per filetype, but this list is kept short in order to prevent slowing down Vim
short in order to prevent slowing down Vim or trying to run conflicting or trying to run conflicting checks. The command `:SyntasticInfo` will show you
checkers. The same command `:SyntasticInfo` will also show you which checkers which checkers are enabled. You can tell syntastic which checkers (among the
are enabled. You can tell syntastic which checkers you want to run by setting available ones) you want to run by setting `g:syntastic_<filetype>_checkers` in
`g:syntastic_<filetype>_checkers` in your `vimrc` (see [below](#faqcheckers)). your `vimrc` (see [below](#faqcheckers)).
Another reason it could fail is that either the command line options or the 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 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 have the latest version of the syntax checker installed. If it still fails then
create an issue - or better yet, create a pull request. post an [issue][4] - or better yet, create a pull request.
<a name="faqpython3"></a> <a name="faqpython3"></a>

2
plugin/syntastic.vim
View File

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