Commit Graph

6 Commits

Author SHA1 Message Date
Austin Ziegler
cfd41f1ca3 Enable user-specified Ruby interpreters.
On systems where Ruby 1.8.7 is the default Ruby and users use
alternative suffixes (e.g., ruby19) or even rbenv or rvm Rubies, modern
Ruby syntax will be highlighted as an error.

The default behaviour in Syntastic is to run 'ruby' to check the syntax
of the script in question. This patch allows the user to specify a
different binary which may even be a full path. This should work on all
platforms.

  let g:syntastic_ruby_exec = 'ruby19'
  let g:syntastic_ruby_exec = '~/.rbenv/versions/1.9.2-p318/bin/ruby'
2012-07-24 13:08:22 +01:00
Martin Grenfell
6818c45710 ruby/mri checker: fix a compatibility bug
The commit 0f73bbaf14 fixed compatibility
with ruby >= 1.9.3 but broke compatibility for ruby < 1.9.3
2012-07-19 11:10:05 +01:00
Frank Schumacher
0f73bbaf14 Fix warning suppression in MRI 1.9.3 2012-07-19 11:25:49 +02:00
Martin Grenfell
6e2b7dd190 ruby/mri checker: make it display warnings
Previously we were using "medium verbosity" with `-W1`. The reason for
this is because using full verbosity caused some bogus repeated warnings
to appear in rspec files.

Enable full verbosity again and filter out the bogus warnings.

Closes #290
2012-07-17 22:39:13 +01:00
Hong Xu
30d7462249 Remove some unnecessary win64 checks.
has('win32') is always true on Win64.
2012-05-08 20:31:20 +08:00
Martin Grenfell
630a57dfef ruby: add the structure for jruby support
* move the existing ruby checker to syntax_checkers/ruby/mri.vim
* add a skeleton checker for jruby
* load mri by default but add an option to specify which ruby checker to
  load

This is in response to #185
2012-03-02 17:38:39 +00:00