Databases
StackOverflow2013
Postsdbo
POOptionParser to parse arguments form file instead of command line
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOptionParser to parse arguments form file instead of command line
    primarykey
    data
    text
    <p>I am using Ruby to execute a code that takes command line arguments. now i trying to use the same program with differnt options so i am putting the options in a file and i want the program to read each line interpret the options and execute the program accordingly.</p> <p>but i get this error. "C:/Ruby193/lib/ruby/1.9.1/optparse.rb:1348:in <code>block in parse_in_order': undefined method</code>shift' for "--c execue --query unix --Servername abc123":String (NoMethodError)"</p> <p>i understand that its reading the file and treating the line as string. but wondering if there is a way to overcome this shift error and treat the line as if it was entered in command prompt. or any better solution.</p> <p>here is my code.</p> <pre><code>require 'optparse' require 'micro-optparse' # --command execue --query unix command --Servername abc123 f =File.open("list_of_commands.txt", "r") f.each_line { |line| line= line.chomp #line = "--c execue --query unix --Servername abc123" #line = eval("\"#{line}\"") puts line options = {} OptionParser.new do |opts| opts.on("-c", "--command result,execue,chart,scpfile", String, "Single command to execute ") do |c| options[:comd] = c end opts.on("-q", "--query remote command, unix command", String, "performs the command on local or remote machine") do |q| options[:query] = q end opts.on("-s", "--servername CHSXEDWDC002 ", String, "server name to execute the command") do |v| options[:hname] = v end opts.on_tail('-h', '--help', 'Show this message') do puts opts exit end end.parse!(line) p options } </code></pre> <p>the contents of the file are below --c execue --query unix --Servername abc123</p> <p>i also tried to use micro-optparse but facing same error. any workaround ?</p> <p><strong>Update:</strong> as per suggestion from "@mu is too short" i tried below options. end.parse!("#{Shellwords.shellsplit(line)}") and/or end.parse!(Shellwords.shellsplit(line)). but none of them worked. </p> <p>i also tried to split the line as array using "line = line.split("\t")" and then end.parse!(line). out put as --c execue --query unix --Servername abc123</p> <p>but now i get error as block in : invalid option --c execute </p> <p><strong>Update:#2</strong> looking at the error, the issue is with the wrong parameter(-c. but thanks to user <strong>"@mu is too short"</strong> for suggesting to use Array.</p> <p><strong>Update: 3</strong> passing the array only worked for short form of the arguments such as -c but when long form was supplied it failed with invalid argument erorr. </p> <p>i dont see much documentation on the optparse. i even tried micro-parse but it requres default valuves and its not an option for me :(</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser2300908
    1. USuser2300908
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload