ruby.git/lib/irb/color.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] Add black and white color to IRB::Color

2023-08-11T16:03:11+00:00

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

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

[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] Fix colorize backtick symbol

2023-02-12T20:27:32+00:00

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

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

Co-authored-by: Stan Lo

[ruby/irb] Assert lvars_code doesn't include \n

2022-10-18T06:03:23+00:00

Removing /\A.+\n/ could have an unexpected impact, depending on how
RubyLex.generate_local_variables_assign_code is implemented. It feels
like a too much assumption and the intention isn't immediately clear,
so I added these changes.

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

[ruby/irb] Always use local variables in current context to parse code (https://github.com/ruby/irb/pull/397)

2022-10-18T05:44:07+00:00

* Use local_variables for colorize, code_block_open check, nesting_level and assignment_expression check

* Check if expression is an assignment BEFORE evaluating it. evaluate might define new localvars and change result of assignment_expression?

* Add local_variables dependent code test

* pend local variable dependent test on truffleruby

code_block_open is not working on truffleruby

* Always pass context to RubyLex#lex

* Rename local_variable_assign_code generator method name

* Add assignment expression truncate test

* Add Context#local_variables and make generate_local_variables_assign_code more simple

* Update lib/irb/input-method.rb

Co-authored-by: Stan Lo 

* Add a comment why assignment expression check should be done before evaluate

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

Co-authored-by: Stan Lo 
Co-authored-by: Takashi Kokubun

[ruby/irb] Rewrite on_scan proc to be more readable.

2022-09-21T15:37:40+00:00

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

[ruby/irb] Scan every single characters in IRB::Color.scan

2022-09-21T15:37:38+00:00

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

[ruby/irb] Color.colorable? needs to consider the condition when irb is not loaded

2022-06-28T13:57:17+00:00

ruby/debug uses `irb/color` selectively:
https://github.com/ruby/debug/blob/0ac22406bb8f65bc76f9f5576a00c729cac693af/lib/debug/color.rb#L4

And in that case, `IRB.conf` won't be defined. So Color.colorable? needs
to consider that.

This also fixes the Ruby trunk CI.

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

[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