From 5b0d3dc8bcbd57e58ea2d7fd3fac9166f82a30b9 Mon Sep 17 00:00:00 2001 From: LCD 47 Date: Sat, 14 Mar 2015 07:32:43 +0200 Subject: [PATCH] README: rephrase. --- README.markdown | 10 +++++----- plugin/syntastic.vim | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.markdown b/README.markdown index 0246ed84..6c6fab4f 100644 --- a/README.markdown +++ b/README.markdown @@ -199,7 +199,7 @@ 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 +shell 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"') @@ -210,10 +210,10 @@ on UNIX and Mac OS-X systems, or ``` 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 -post an [issue][4] - or better yet, create a pull request. +Finally, 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 post an [issue][4] - or better yet, create a pull request. diff --git a/plugin/syntastic.vim b/plugin/syntastic.vim index f2ef9bc6..84af7ac9 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-56' +let g:_SYNTASTIC_VERSION = '3.6.0-57' lockvar g:_SYNTASTIC_VERSION " Sanity checks {{{1