Ctrl-D behaviour is different between normal IRB and irb:rdbg sessions
st0012 opened this issue · 2 comments
st0012 commented
Description
In normal IRB sessions, ctrl-D is the same as exit, which exits the current IRB session. In irb:rdbg sessions, ctrl-D is executed by debug, which is the same as its quit command and will leave the entire process.
So in the a process that has multiple breakpoints, ctrl-D is semantically similar to continue. But once irb:rdbg is activated, ctrl-D's behaviour changes. This adds cognitive load to users as they need to be aware of the type of sessions they're in to perform the intended action.