From: "konsolebox (K B)" <noreply@...>
Date: 2022-05-19T00:15:54+00:00
Subject: [ruby-core:108615] [Ruby master Bug#18783] OptionParser should recognize "-" as an optional argument

Issue #18783 has been updated by konsolebox (K B).


Any thoughts on this?

I created a PR: https://github.com/ruby/ruby/pull/5918


----------------------------------------
Bug #18783: OptionParser should recognize "-" as an optional argument
https://bugs.ruby-lang.org/issues/18783#change-97652

* Author: konsolebox (K B)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.7.4p191, ruby 3.1.2p20
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
``` ruby
require 'optparse'

optarg = nil

OptionParser.new do |parser|
  parser.on("-o", "--opt [ARG]", "Option with optional argument") do |arg|
    optarg = arg
  end
end.parse!

puts "#{optarg.inspect}, #{ARGV.inspect}"
```
Executing the code above with `-o -` as arguments outputs `nil, ["-"]` when it should produce `"-", []` instead.

OptionParser recognizes `-` as a general non-option argument but it doesn't do the same when `-` follows an option with an optional argument.

In my shell script, I consider options as `-?*` (glob) instead of `-*` so `-` is also considered as a valid argument.  Perhaps OptionParser should do the same.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>