From: nobu@... Date: 2019-12-22T16:10:01+00:00 Subject: [ruby-core:96410] [Ruby master Misc#16444] What is the reason for the warning of IRB? Issue #16444 has been updated by nobu (Nobuyoshi Nakada). A patch to suppress the warning when started as `console`. ```diff diff --git a/lib/irb/init.rb b/lib/irb/init.rb index 2af872fd03..464b33ae03 100644 --- a/lib/irb/init.rb +++ b/lib/irb/init.rb @@ -31,6 +31,8 @@ @TRACER_INITIALIZED = false # default configurations + @CONF[:USE_MULTILINE] = true if ap_path + unless ap_path and @CONF[:AP_NAME] ap_path = File.join(File.dirname(File.dirname(__FILE__)), "irb.rb") end ``` ---------------------------------------- Misc #16444: What is the reason for the warning of IRB? https://bugs.ruby-lang.org/issues/16444#change-83335 * Author: y-yagi (Yuji Yaginuma) * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Ruby 2.7 always shows a warning when starting IRB. Why is this necessary? Of course, ways to suppress the warning have been suggested. However, libraries that extend IRB, such as `rails console` and `aruba`, may not receive arguments equivalent as IRB. In this case, trying to run as suggested in this proposal(e.g. run `rails console` with `--legacy` argument) will result in an error. I think this can be confusing for users. If have not major known issues, I think we can keep the current behavior without warning. On the other hand, if there is already an issue, isn't the better for the old behavior by default? Thanks. -- https://bugs.ruby-lang.org/ Unsubscribe: