B
Bryan Richardson
[Note: parts of this message were removed to make it a legal post.]
Hello All,
I'm hoping someone can help me get around a problem I'm having. I have a
Ruby command-line program where I use OptionParser to parse the program's
options. This program is a wrapper for a bunch of other programs, each of
which also accept command-line options. A typical run command would look
like this:
#> wrapper_app --script-to-run MyScript --script-options "--input
foo.txt--output
bar.txt"
Where the information passed with --script-options is the options to use for
the script to be ran. However, OptionParser in my main wrapper program
attempts to parse the options given by --script-options and throws an error
because they aren't valid options for the main wrapper program. I was
hoping that surrounding them in quotes would cause it to be seen as a single
input string to --script-options but that doesn't seem to be the case. Does
anyone know how I can do what I'm trying to do?
Thanks in advance!!! -- BTR
Hello All,
I'm hoping someone can help me get around a problem I'm having. I have a
Ruby command-line program where I use OptionParser to parse the program's
options. This program is a wrapper for a bunch of other programs, each of
which also accept command-line options. A typical run command would look
like this:
#> wrapper_app --script-to-run MyScript --script-options "--input
foo.txt--output
bar.txt"
Where the information passed with --script-options is the options to use for
the script to be ran. However, OptionParser in my main wrapper program
attempts to parse the options given by --script-options and throws an error
because they aren't valid options for the main wrapper program. I was
hoping that surrounding them in quotes would cause it to be seen as a single
input string to --script-options but that doesn't seem to be the case. Does
anyone know how I can do what I'm trying to do?
Thanks in advance!!! -- BTR