Skip to content
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

Ctrl-D behaviour is different between normal IRB and irb:rdbg sessions #921

Open
st0012 opened this issue Apr 11, 2024 · 0 comments
Open

Comments

@st0012
Copy link
Member

st0012 commented Apr 11, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant