Issue #16444 has been updated by shevegen (Robert A. Heiler).


Agreed for compatibility - may be better to retain the old behaviour as-is.

I believe it was not a deliberate change but an oversight since the author
of reline here on the issue tracker also mentioned compatibility being
an important goal for the rewrite, about a year ago; matz also mentioned
this.

Hopefully that may be fixed before xmas. :)

----------------------------------------
Misc #16444: What is the reason for the warning of IRB? 
https://bugs.ruby-lang.org/issues/16444#change-83326

* 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 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>