-
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
Deprecate multi-irb feature #653
Comments
Please consider reusing the old command names. |
Hi. I find bin/rails console
# assume it's part of the application
class Greeter
def hello = "Hello, World!"
end
g = Greeter.new
irb g # <-----------------
Multi-irb commands are deprecated [...]
irb#1(#<Greeter:0x00007faa7b850188>):001> hello
=> "Hello, World!"
UPDATE: OK, just realized that it's
Is there a way to go back without having first to push current workspace to the stack? pry example:
My impression is that |
I love how this got implemented.... Now whenever I try to assign to an instance variable with the name |
This implementation is a bit overly aggressive. As @jwkoelewijn points out, it breaks any code we might type or copy-paste that uses a
Is there a way we can not break assignment to a variable named |
Usability problem of local variable and command is fixed in #961 and released
|
Sweet, thanks! 🙌🏼 |
Something I miss without being able to just run irb(main):002:0> File.open("/etc/hosts") { |f| irb f }
irb#1(#<File:0x000055be023ef240>):001:0> self.size
=> 174 and then being able to iteratively experiment with methods on the object yielded to the block. Is there an equivalent version that works without multi-irb? [EDIT: Oh, maybe I should just be using irb(main):001> File.open("/etc/hosts") { |f| binding.irb }
irb(main):001> f.size
=> 1063 ] |
Plan
irb
,jobs
,fg
, andkill
in the next minor releasev2.0.0
Reasons
chws
,pushws
...etc.Feedback wanted
If you use the multi-irb feature and don't want to see it deprecated from IRB, please leave a comment below to explain your use case of it. It will help us assess this plan.
The text was updated successfully, but these errors were encountered: