-
Notifications
You must be signed in to change notification settings - Fork 121
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
as _default_ debug
front-end?
#712
Comments
After chatting with the maintainer of
|
Sweet!
Fair 'nuff! Any idea what the best way to follow this development is? Ready to upgrade my |
I've opened ruby/debug#1024 upstream to make its |
Understandable! Thank you for this 🙏 I've been spending more time lately kicking into |
Woop woop! Out of curiosity, did ruby/debug#1024 include this functionality?
|
@jon-sully Yes it does 😄 |
Description
Greetings! I've been playing with the new☺️
irb/debug
integration that was recently released and overall the experience is really great. Having fullirb
context while being in a fulldebug
session is really nice. Theirb:rdbg
prompt is easy to work with and simple — kudos!I'm hoping we can improve the experience a bit though. My understanding is that right now the only way to properly enter this context/experience is to use
binding.irb
to halt the code, then once in thatirb
session, manually calldebug
.After migrating to the debug gem after years of pry/byebug, it took some time for me to retrain my muscle memory for debugging to use
debugger
rather thanbinding.pry
etc. but I've found that even withirb
's new front-end integration working with the debug gem, thedebugger
still only loads the default debug front end. Is there any way that we could consolidate the whole experience such that simply usingdebugger
drops into the fullirb:rdbg
session?The text was updated successfully, but these errors were encountered: