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

FAQ, manual: use the proper buzzwords for Ruby version managers. (@lloeki)

Browse Source
This commit is contained in:
LCD 47 2017-08-07 11:48:49 +03:00
parent e1161a723a
commit a835b0ada1
3 changed files with 21 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.markdown
View File

@ -437,15 +437,15 @@ scripts.
__4.12. Q. How can I check scripts written for different versions of Ruby?__
A. Install a Ruby version manager such as [rvm][rvm] or [rbenv][rbenv],
activate the environment for the relevant version of Ruby, and install in it
the checkers you want to use. Set `g:syntastic_ruby_checkers` accordingly in
your `vimrc`, and run [Vim][vim] from the virtual environment.
activate the relevant version of Ruby, and install in it the checkers you want
to use. Set `g:syntastic_ruby_checkers` accordingly in your `vimrc`, and run
[Vim][vim] under the relevant Ruby version.
If you're starting Vim from a desktop manager rather than from a terminal you
might need to write wrapper scripts around your checkers, to activate the
virtual environment before running the actual checks. Then you'll need to
point the relevant `g:syntastic_ruby_<checker>_exec` variables to the wrapper
scripts.
If you're starting Vim from a desktop manager rather than from a terminal
and depending on the version manager you use you might need to write wrapper
scripts around your checkers, to activate the relevant version of Ruby
before running the actual checks. Then you'll need to point the relevant
`g:syntastic_ruby_<checker>_exec` variables to the wrapper scripts.
<a name="faqperl"></a>

22
doc/syntastic-checkers.txt
View File

@ -5720,11 +5720,12 @@ running "rubocop --version" from the shell. If it complains about "Parser"
"Ruby" than you are running, your configuration is not directly supported by
syntastic.
While passing around the blame for this does have a certain entertaining value
(cf. https://github.com/bbatsov/rubocop/issues/1819), the problem is real,
since "Ruby" syntax did change between versions. The solution is to run a
system such as "rbenv" (http://rbenv.org/) or "rvm" (https://rvm.io/), that
allows you to run multiple versions of "Ruby" without conflicts: >
While passing around the blame for this does have a certain entertaining
value (cf. https://github.com/bbatsov/rubocop/issues/1819), the problem
is real, since "Ruby" syntax did change between versions. The solution
is to run a version manager such as "rbenv" (http://rbenv.org/) or "rvm"
(https://rvm.io/), that allows you to run multiple versions of "Ruby" without
conflicts: >
$ rbenv version
2.1.3 (set by /usr/local/var/rbenv/version)
@ -5768,11 +5769,12 @@ running "ruby-lint --version" from the shell. If it complains about "Parser"
"Ruby" than you are running, your configuration is not directly supported by
syntastic.
While passing around the blame for this does have a certain entertaining value
(cf. https://github.com/bbatsov/rubocop/issues/1819), the problem is real,
since "Ruby" syntax did change between versions. The solution is to run a
system such as "rbenv" (http://rbenv.org/) or "rvm" (https://rvm.io/), that
allows you to run multiple versions of "Ruby" without conflicts: >
While passing around the blame for this does have a certain entertaining
value (cf. https://github.com/bbatsov/rubocop/issues/1819), the problem
is real, since "Ruby" syntax did change between versions. The solution
is to run a version manager such as "rbenv" (http://rbenv.org/) or "rvm"
(https://rvm.io/), that allows you to run multiple versions of "Ruby" without
conflicts: >
$ rbenv version
2.1.3 (set by /usr/local/var/rbenv/version)

2
plugin/syntastic.vim
View File

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