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

README: add a note about loading syntastic as a Vim package.

Browse Source
This commit is contained in:
LCD 47 2016-03-06 23:16:57 +02:00
parent b9620a60b7
commit 5057b5effb
2 changed files with 12 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.markdown
View File

@ -105,6 +105,12 @@ Syntastic should work with any modern plugin managers for Vim, such as
[Vundle][17]. Instructions for installing syntastic with [Pathogen][1] are [Vundle][17]. Instructions for installing syntastic with [Pathogen][1] are
included below for completeness. included below for completeness.
Starting with Vim version 7.4.1486 you can also load syntastic using the
standard mechanism of packages, without the help of third-party plugin managers
(see `:help packages` in Vim for details). Please note that, while support for
packages has been added in Vim 7.4.1384, only versions 7.4.1486 and later have
all functionality needed by syntastic.
Last but not least: syntastic doesn't know how to do any syntax checks by Last but not least: syntastic doesn't know how to do any syntax checks by
itself. In order to get meaningful results you need to install external itself. In order to get meaningful results you need to install external
checkers corresponding to the types of files you use. Please consult the checkers corresponding to the types of files you use. Please consult the
@ -254,11 +260,11 @@ __4.4. Q. The `perl` checker has stopped working...__
A. The `perl` checker runs `perl -c` against your file, which in turn A. The `perl` checker runs `perl -c` against your file, which in turn
__executes__ any `BEGIN`, `UNITCHECK`, and `CHECK` blocks, and any `use` __executes__ any `BEGIN`, `UNITCHECK`, and `CHECK` blocks, and any `use`
statements in your file (cf. [perlrun][10]). This is probably fine if you statements in your file (cf. [perlrun][10]). This is probably fine if you
wrote the file yourself, but it's a security problem if you're checking third wrote the file yourself, but it's a security problem if you're checking
party files. Since there is currently no way to disable this behaviour while third-party files. Since there is currently no way to disable this behaviour
still producing useful results, the checker is now disabled by default. To while still producing useful results, the checker is now disabled by default.
(re-)enable it, make sure the `g:syntastic_perl_checkers` list includes `perl`, To (re-)enable it, make sure the `g:syntastic_perl_checkers` list includes
and set `g:syntastic_enable_perl_checker` to 1 in your `vimrc`: `perl`, and set `g:syntastic_enable_perl_checker` to 1 in your `vimrc`:
```vim ```vim
let g:syntastic_enable_perl_checker = 1 let g:syntastic_enable_perl_checker = 1
``` ```

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.7.0-94' let g:_SYNTASTIC_VERSION = '3.7.0-95'
lockvar g:_SYNTASTIC_VERSION lockvar g:_SYNTASTIC_VERSION
" Sanity checks {{{1 " Sanity checks {{{1