ruby--ruby/libexec/irb

#!/usr/bin/env ruby
#
#   irb.rb - interactive ruby
#   	$Release Version: 0.9.6 $
#   	$Revision$
#   	by Keiju ISHITSUKA(keiju@ruby-lang.org)
#

require "irb"

IRB.start(__FILE__)
Use stub executables generated by RubyGems istead of original executables. It resolved the conflict issues when invoking `gem i rdoc` and the binstub issues with Bundler and Rails. [Bug #5060][ruby-core:38257][Fix GH-2023] * https://github.com/rubygems/rubygems/pull/2338 * https://github.com/heroku/heroku-buildpack-ruby/issues/829 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65963 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-11-24 20:20:00 -05:00			`#!/usr/bin/env ruby`
			`#`
			`# irb.rb - interactive ruby`
			`# $Release Version: 0.9.6 $`
			`# $Revision$`
			`# by Keiju ISHITSUKA(keiju@ruby-lang.org)`
			`#`

[ruby/irb] require_relative can't be used for default gems' exe files The `exe` folder and `lib` folder of default gems don't locate under the same place. While `exe/irb` will be under the gem folder, `irb.rb` will be under `lib/ruby/VERSION/`. So `require_relative` will make `irb` unuseable when shipped with Ruby. Related discussion in the comments: https://github.com/ruby/irb/pull/335 https://github.com/ruby/irb/commit/99d3aa979d 2022-01-17 10:17:18 -05:00			`require "irb"`
Use stub executables generated by RubyGems istead of original executables. It resolved the conflict issues when invoking `gem i rdoc` and the binstub issues with Bundler and Rails. [Bug #5060][ruby-core:38257][Fix GH-2023] * https://github.com/rubygems/rubygems/pull/2338 * https://github.com/heroku/heroku-buildpack-ruby/issues/829 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65963 b2dd03c8-39d4-4d8f-98ff-823fe69b080e 2018-11-24 20:20:00 -05:00
			`IRB.start(__FILE__)`