-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IRB crashes by completion on the first line before long line #308
Comments
ima1zumi
added a commit
to ima1zumi/reline
that referenced
this issue
Nov 17, 2021
Look good to me. Thanks. I've tried that with
But another input kills irb again.
And hit up arrow key to start editing, then type
|
ima1zumi
added a commit
to ima1zumi/reline
that referenced
this issue
Nov 19, 2021
ima1zumi
added a commit
to ima1zumi/reline
that referenced
this issue
Nov 20, 2021
fix ruby/irb#308 This bug occurred when `dialog.width - calculate_width(s, true)` was negative. When `dialog.width` is shorter than `old_dialog.width`, it calculates how much padding it has to do. However, there are cases where `s` is longer than `dialog.width`, as in the issue. In that case, `padding_space_with_escape_sequences` will crash. Here, `old_dialog.width` is longer than `dialog.width`, so I changed the padding width to `old_dialog.width - dialog.width`.
matzbot
pushed a commit
to ruby/ruby
that referenced
this issue
Nov 21, 2021
fix ruby/irb#308 This bug occurred when `dialog.width - calculate_width(s, true)` was negative. When `dialog.width` is shorter than `old_dialog.width`, it calculates how much padding it has to do. However, there are cases where `s` is longer than `dialog.width`, as in the issue. In that case, `padding_space_with_escape_sequences` will crash. Here, `old_dialog.width` is longer than `dialog.width`, so I changed the padding width to `old_dialog.width - dialog.width`. ruby/reline@c581c31e0f
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
ra
looks like asResult of irb_info
The text was updated successfully, but these errors were encountered: