Actions
Bug #15738
closedRUBYOPT disables have precedence over the command line
Status:
Closed
Assignee:
-
Target version:
-
ruby -v:
ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
Description
From #15736:
It seems unexpected that the command line argument doesn't override the RUBYOPT options:
$ RUBYOPT=--disable-gems ruby --enable=gems -e 'p defined?(Gem)'
nil
That seems a bug. I would expect the command line arguments always override RUBYOPT
arguments.
This:
$ ruby --disable=gems --enable=gems -e 'p defined?(Gem)'
"constant"
$ ruby --enable=gems --disable=gems -e 'p defined?(Gem)'
nil
works as expected.
Actions
Like0
Like0Like0Like0