| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/dc59afe4f6
|
|
|
|
| |
https://github.com/ruby/irb/commit/13572d8cdc
|
|
|
|
| |
https://github.com/ruby/irb/commit/0a641a69b0
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/dd56e06df5
|
|
|
|
| |
https://github.com/ruby/irb/commit/6184b227ad
|
|
|
|
|
| |
`irb` doesn't run because this file isn't included in the gem.
https://github.com/ruby/irb/commit/73cda56d25
|
|
|
|
| |
https://github.com/ruby/irb/commit/a71753f15a
|
|
|
|
| |
https://github.com/ruby/irb/commit/5d628ca40e
|
|
|
|
|
|
|
|
|
|
|
|
| |
A closed brace in auto-indent shouldn't affect the next brace in the same line,
but it behaves like below:
p() {
}
It's a bug.
https://github.com/ruby/irb/commit/fbe59e344f
|
|
|
|
|
|
|
| |
IRB::InputCompletor::PerfectMatchedProc crashes when doc not found because a
variable name was incorrect.
https://github.com/ruby/irb/commit/889fd4928f
|
|
|
|
| |
https://github.com/ruby/irb/commit/8f1ab2400c
|
|
|
|
| |
https://github.com/ruby/irb/commit/e37dc7e58e
|
| |
|
|
|
|
| |
https://github.com/ruby/irb/commit/9eb1801a66
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rails before 5.2 added Array#append as an alias to Array#<< ,
so that it expects only one argument.
However ruby-2.5 added Array#append as an alias to Array#push
which takes any number of arguments.
If irb completion is used in `rails c` (for example "IO.<tab>")
it fails with:
irb/completion.rb:206:in `<<': wrong number of arguments (given 3, expected 1) (ArgumentError)
Using Array#push instead of Array#append fixes compatibility.
https://github.com/ruby/irb/commit/5b7bbf9c34
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/ruby/irb/issues/55
If we had put multiple open braces on a line the with no closing brace
spaces_of_nest array keeps getting '0' added to it. This means that when
we pop off of this array we are saying that we should be in position zero
for the next line. This is an issue because we don't always want to be
in position 0 after a closing brace.
Example:
```
[[[
]
]
]
```
In the above example the 'spaces_of_nest' array looks like this after
the first line is entered: [0,0,0]. We really want to be indented 4
spaces for the 1st closing brace 2 for the 2nd and 0 for the 3rd. i.e.
we want it to be: [0,2,4].
We also saw this issue with a heredoc inside of an array.
```
[<<FOO]
hello
FOO
```
https://github.com/ruby/irb/commit/80c69c8272
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit fixes the check_newline_depth_difference method to multiple
open braces on one line into account. Before this change we were
subtracting from the depth in check_newline_depth_difference on
every open brace. This is the right thing to do if the opening and
closing brace are on the same line. For example in a method definition we
have an opening and closing parentheses we want to add 1 to our depth,
and then remove it.
```
def foo()
end
```
However this isn't the correct behavior when the brace spans multiple
lines. If a brace spans multiple lines we don't want to subtract from
check_newline_depth_difference and we want to treat the braces the same
way as we do `end` and allow check_corresponding_token_depth to pop the
correct depth.
Example of bad behavior:
```
def foo()
[
]
puts 'bar'
end
```
Example of desired behavior:
```
def foo()
[
]
puts 'bar'
end
```
https://github.com/ruby/irb/commit/7dc8af01e0
|
|
|
|
| |
https://github.com/ruby/irb/commit/8da0c74640
|
|
|
|
| |
https://github.com/ruby/irb/commit/d9a7844f50
|
|
|
|
|
|
| |
Follow up of the previous commit
https://github.com/ruby/irb/commit/ab207353d3
|
|
|
|
|
|
| |
Fixes #47
https://github.com/ruby/irb/commit/6b8eca4635
|
|
|
|
| |
Fixed misspellings reported at [Bug #16437], for default gems.
|
|
|
|
| |
https://github.com/ruby/irb/commit/da6577a88c
|
|
|
|
| |
https://github.com/ruby/irb/commit/4be3158358
|
|
|
|
|
|
|
|
|
|
|
| |
String#grapheme_clusters"
This reverts commit 2b0b19b87c60d2cdb329979acbb96e12a1f940e7.
New IRB parser needs new Ripper what has lex_state too. The new Ripper is
adopted by Ruby 2.5 or later.
https://github.com/ruby/irb/commit/9ab6e35a2c
|
|
|
|
| |
https://github.com/ruby/irb/commit/2b0b19b87c
|
| |
|
|
|
|
|
|
| |
"IRB::InputMethod#eof?" requires eof status each user input but
"ReidlineInputMethod#eof?" used "Reline.eof?" what is singleton data.
"ReidlineInputMethod#eof?" is changed to use the result of user input.
|
|
|
|
|
|
| |
This reverts commit 5e275dd2af4d9d24cdb1cfc0f232f348dae9c2cd.
...The @1 type numberd parameter is reverted from Ruby syntax.
|
|
|
|
|
|
| |
IRB completion logic always needed exponential notation for complex literal
such as 3e6i but it's bug. I fixed to support complex literal without
exponential notation such as 3i.
|
| |
|
| |
|
|
|
|
| |
I'm not sure, but maybe it was gramatically incorrect?
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|