ruby.git/lib/irb/cmd/nop.rb, branch v3_3_11

[Bug #20511] Update reline-0.5.7 (#10848)

2024-05-28T22:54:39+00:00

* Update reline-0.5.7

* Update irb-1.13.1

[ruby/irb] Refactor ExtendCommand::Nop

2023-06-05T19:12:16+00:00

(https://github.com/ruby/irb/pull/598)

* Rename conf to irb_context

* Drop Nop#irb method because it's only used by irb/ext/loader.rb

We don't need to expose this method to all command classes, especially
when it's just an alias of `irb_context.irb`.

[ruby/irb] Drop Ruby 2.6 support

2023-04-05T21:40:40+00:00

(https://github.com/ruby/irb/pull/555)

* Remove all Ruby 2.6 support

* Drop Ruby 2.6 specific testing conditions

* Only run Ruby 2.7+ on CI

* Bump Ruby requirement to 2.7+

https://github.com/ruby/irb/commit/3f714b616c

[ruby/irb] Don't check RUBY_ENGINE when deciding whether to accept kargs

2023-04-02T15:34:28+00:00

Ruby implementations like JRuby and TruffleRuby already indicate their
compatibility target with RUBY_VERSION. We don't need to exclude
them from accepting keyword arguments as long as they target 2.7+.

https://github.com/ruby/irb/commit/bf20faa4e6

Co-authored-by: Kevin Menard

[ruby/irb] Formatting to header styles

2023-01-11T22:29:10+00:00

https://github.com/ruby/irb/commit/cef125850d

[ruby/irb] Removed Release Version and Revisions for old VCS software

2023-01-11T22:29:09+00:00

https://github.com/ruby/irb/commit/07fae94862

[ruby/irb] `show_doc` command should take non-string argument too

2022-12-12T17:35:48+00:00

(https://github.com/ruby/irb/pull/478)

Given that `show_doc` already supports syntax like `String#gsub`, it
should be able to take it in non-string form too, like `edit` and
`show_source` do. This ensures users can have a consistent syntax on
argument between different commands.

[ruby/irb] Gracefully handle missing command argument

2022-12-08T21:05:37+00:00

(https://github.com/ruby/irb/pull/473)

* Handle file loading commands' argument error gracefully

Currently, if users don't provide an argument to `source`,
`irb_load`, and `irb_require`, IRB raises `ArgumentError` with full
stacktrace. This is confusing because it looks similar to when IRB has
internal issues. The message also isn't helpful on helping users avoid
the error.

So in this commit, I add a new `CommandArgumentError` for commands to
raise explicitly when users' input doesn't satisfy a command's argument
requirement.

* Gracefully handle `fg` command's argument requirement

[ruby/irb] Add "show_cmds" command to list all commands'

2022-12-08T19:10:23+00:00

descriptions
(https://github.com/ruby/irb/pull/463)

https://github.com/ruby/irb/commit/7e857655ac

[ruby/irb] Centralize coloring control (https://github.com/ruby/irb/pull/374)

2022-06-28T13:30:42+00:00

* Use colorable: argument as the only coloring control

* Centalize color controling logic at Color.colorable?

There are 2 requirements for coloring output:

1. It's supported on the platform
2. The user wants it: `IRB.conf[:USE_COLORIZE] == true`

Right now we check 1 and 2 separately whenever we colorize things.
But it's error-prone because while 1 is the default of `colorable`
parameter, 2 always need to manually checked. When 2 is overlooked, it
causes issues like https://github.com/ruby/irb/pull/362

And there's 0 case where we may want to colorize even when the user
disables it. So I think we should merge 2 into `Color.colorable?` so it
can be automatically picked up.

* Add tests for all inspect modes

* Simplify inspectors' coloring logic

* Replace use_colorize? with Color.colorable?

* Remove Context#use_colorize cause it's redundant

https://github.com/ruby/irb/commit/1c53023ac4