Passing arguments to a ruby script while using the expanded rvm command line syntax?

Question

The rvm command lets you tell it what environment you want to use and pass a block to it to invoke a script or something (for a one-time run of the command) e.g.:

rvm 1.9.2-p290@whatever-gemset do ruby my-script.rb

However, if the script accepts command line arguments as well and you try to pass them script at invocation, rvm complains. Does anyone know if rvm has syntax to support/allow this?

e.g.:

rvm 1.9.2-p290@whatever-gemset do ruby my-script.rb -p
ERROR: Unrecognized command line argument(s): '-p' ( see: 'rvm usage' )

Does putting your command in quotes work? do "ruby my-script.rb -p" — tadman
– tadman, Commented Jun 6, 2012 at 16:01
Actually, it does for me... However, a coworker of mine is getting some weird behavior when trying to do it that way which may just be specific to his environment. In any case, you've answered my question and for that I thank you. — donovan.lampa
– donovan.lampa, Commented Jun 6, 2012 at 16:53

tadman · Accepted Answer · 2012-06-06 17:32:01Z

1

To avoid rvm trying to parse those parameters as arguments to rvm itself, put them in quotes to pass them as a single argument:

rvm 1.9.2-p290@whatever-gemset do "ruby my-script.rb -p"

The only reason this would fail is if some kind of shell-expansion is being done before this command is actually executed which is non-standard behavior.

answered Jun 6, 2012 at 17:32

tadman

212k23 gold badges237 silver badges266 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

mpapis Over a year ago

also it would be good idea to open a bug report github.com/wayneeseguin/rvm/issues - the arguments after do should not be parsed.

tadman Over a year ago

A naive argument parser will always make this mistake. Even Ruby's option parsers will fall for this unless you use the -- separator to manually turn off argument parsing. The way to fix this is to pre-process the command-line arguments and only feed in a subset to your option parser. It does sound like a bug, though.

mpapis Over a year ago

in rvm do should behave like --, there are few rvm sub-commands that when it just stop processing and pass arguments to sub-command handler, i do not know why it did not worked for do, but with the bug report i will have a note to check it later.

Collectives™ on Stack Overflow

Passing arguments to a ruby script while using the expanded rvm command line syntax?

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related