Ctrl+C exits debugger from repl v4.0.0

[LMS007]

I thought this was fixed, but I guess I'm still having this issue. Command-line debugging is painful enough, this needs to be fixed please!

[LMS007]

^ I'm using gitbash with windows 7 (if that should matter)

[jamen]

In a lot of terminals (probably originating from Unix systems or earlier) this is by-design. On Unix, Ctrl+C sends a SIGINT signal to the program. So this has become kind of the general norm in terminal-based environments that Ctrl+C exits. I don't really think this is an issue. :P

Are you trying to copy text? Well, on the topic of "terminal norms", Ctrl+Shift+C is generally what most terminals seem to use to copy text out of them, usually Ctrl+Shift+[key] is the counterpart for Ctrl+[key] in a normal terminal environment.

[Trott]

On OS X, when I fire up the debugger, the first cntl-c results in a message telling me to hit cntl-c again if I want to exit. As long as I don't hit cntl-c twice in a row, it won't exit. Perhaps this issue is Windows-specific.

[LMS007]

Not trying to copy text, I'm just trying to close repl and go back to being able to step through the debugger. I have no way of doing that currently.

[bnoordhuis]

/cc @nodejs/platform-windows

[jasnell]

is this still an issue?

[bzoz]

I guess that #12123 solved this. If it still happens fell free to reopen the issue.