Invalid cursor position after CTRL-C on mac os about prompt

[jfhbrook]

It looks like this is an issue in linux as well. My guess is that a reasonable fix could be to add a .once listener for the ^C event that writes a newline to the stream.

[Marak]

My thoughts were to deep-dive into read and readline module to discover why this happens. I don't think an additional event emitter is needed.

Feel free to research this.

As I took some time to research for solving issues with the ctrl+c handling today, I figured out, that readline and read both don't make any cursor repositioning, because the SIGINT signal is directly given back to top as a error callback.

For repositiong the cursor, inserting a blank line console.log here could set the cursor to the next line.
This could also be done directly in read, but for me both seems kinda way of ... unattractive.

What's your opinion on that?