ruby.git/lib/irb/workspace.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] Support seamless integration with ruby/debug

2023-08-13T18:30:34+00:00

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

* Support native integration with ruby/debug

* Prevent using multi-irb and activating debugger at the same time

Multi-irb makes a few assumptions:

- IRB will manage all threads that host sub-irb sessions
- All IRB sessions will be run on the threads created by IRB itself

However, when using the debugger these assumptions are broken:

- `debug` will freeze ALL threads when it suspends the session (e.g. when
  hitting a breakpoint, or performing step-debugging).
- Since the irb-debug integration runs IRB as the debugger's interface,
  it will be run on the debugger's thread, which is not managed by IRB.

So we should prevent the 2 features from being used at the same time.
To do that, we check if the other feature is already activated when
executing the commands that would activate the other feature.

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

[ruby/irb] Add a comment about Rails' patch on

2023-02-27T15:23:31+00:00

Workspace#filter_backtrace
(https://github.com/ruby/irb/pull/526)

* Add a comment about Rails' patch on Workspace#filter_backtrace

* Update lib/irb/workspace.rb

Co-authored-by: Sorah Fukumori 

---------

https://github.com/ruby/irb/commit/9443d911fc

Co-authored-by: Sorah Fukumori

[ruby/irb] Remove unused context argument from Worksapce#evaluate

2023-02-18T11:34:28+00:00

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

The context argument was introduced in this change:

https://github.com/ruby/irb/commit/6806669d178f90f38b99c144bdfee06bdb93a229#diff-296327851fb7a2c307c2d0693b769f58c01aaf315972f290500d10081ee200a9

perhaps for potential usages. But after that it's never used.

[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] workspace.rb cleanup

2023-01-04T09:35:57+00:00

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

* Remove unnecessary Binding#source_location check

`Binding#source_location` was added in 2.6, which is the minimum supported
version now. So this check is no longer necessary.

* Remove unused IRB.delete_caller

This method was added in the earliest version of IRB:

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

But it's not currently referenced by anything. We can verify this with a
org-wide search result:

https://github.com/search?q=org%3Aruby+delete_caller&type=code

[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

[ruby/irb] Move IRB::TOPLEVEL_BINDING from exe/irb to lib/irb/workspace.rb

2021-09-09T21:37:07+00:00

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

[ruby/irb] Avoid loading files' local variables [Bug #17623]

2021-09-09T21:37:06+00:00

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