Issue #5421 has been updated by Eric Hodel.

Status changed from Open to Rejected

=begin
ruby -r uses RubyGems now, you probably need to upgrade your ruby:

  $ gem19 which nokogiri
  /usr/local/lib/ruby/gems/1.9.1/gems/nokogiri-1.5.0/lib/nokogiri.rb
  $ ruby19 -rnokogiri -ve 'p Nokogiri'
  ruby 1.9.3dev (2011-09-27 revision 33347) [x86_64-darwin11.1.0]
  Nokogiri

  $ ~/.multiruby/install/1.9.2-p290/bin/gem which nokogiri
  /Users/drbrain/.multiruby/install/1.9.2-p290/lib/ruby/gems/1.9.1/gems/nokogiri-1.5.0/lib/nokogiri.rb
  $ ~/.multiruby/install/1.9.2-p290/bin/ruby -rnokogiri -ve 'p Nokogiri'
  ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.0.0]
  Nokogiri

=end

----------------------------------------
Feature #5421: -r option useless
http://redmine.ruby-lang.org/issues/5421

Author: Thomas Sawyer
Status: Rejected
Priority: Normal
Assignee: 
Category: core
Target version: 


Ran into a problem trying to require a plugin I had written while running a ruby scipt, e.g.

  $ ruby -rmyplugin script.rb

It tells me "no such file" for myplugin. Turns out the problem is that the -r option uses internal require code and thus circumvents rubygems or any modified #require, so even though my RUBYOPT="-rubygems", it makes no difference. I've also been informed that RUBYOPT is applied after -r options, which makes for an additional problem. Apparently this so -T can ignore RUBYOPT? But if that's the only reason, then -T should be preparsed from ARGV b/c having -r options load first prevents augmentation and use of what RUBYOPT loads by -r. RUBYOPT is supposed to set the environment, but it isn't much of an environment if its not there when I run a ruby command.

I've marked this report as a feature b/c I'm sure someone would take issue if I did otherwise, but I personally see it as a bug b/c it makes -r useless in many cases. 




-- 
http://redmine.ruby-lang.org