From da1ecc0bb8a02dfb5e5909725bd3c3c52958b7f2 Mon Sep 17 00:00:00 2001 From: LCD 47 Date: Sat, 14 Mar 2015 07:29:06 +0200 Subject: [PATCH] FAQ: add a note about $PATH. --- README.markdown | 14 ++++++++++++++ plugin/syntastic.vim | 2 +- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index 24ac4ab4..0246ed84 100644 --- a/README.markdown +++ b/README.markdown @@ -196,6 +196,20 @@ which checkers are enabled. You can tell syntastic which checkers (among the available ones) you want to run by setting `g:syntastic__checkers` in your `vimrc` (see [below](#faqcheckers)). +A third possible reason is that the `$PATH` seen by syntastic might not be same +as the `$PATH` in your login shell. Syntastic runs checkers using the shell +pointed to by Vim's `shell` (or by `g:syntastic_shell`, if set), and that's the +one you need to configure to set the proper `$PATH` and environment variables +for your checkers. You can see syntastic's idea of `$PATH` by running +```vim +:echo syntastic#util#system('echo "$PATH"') +``` +on UNIX and Mac OS-X systems, or +```vim +:echo syntastic#util#system('echo %PATH%') +``` +on Windows. + 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 diff --git a/plugin/syntastic.vim b/plugin/syntastic.vim index e0260051..f2ef9bc6 100644 --- a/plugin/syntastic.vim +++ b/plugin/syntastic.vim @@ -19,7 +19,7 @@ if has('reltime') lockvar! g:_SYNTASTIC_START endif -let g:_SYNTASTIC_VERSION = '3.6.0-55' +let g:_SYNTASTIC_VERSION = '3.6.0-56' lockvar g:_SYNTASTIC_VERSION " Sanity checks {{{1