Is it really necessary to Ctrl-C on connect?

Hmm, that's a strange one - it works on the build I have here... If I do:

setInterval("",100);
blah [no newline]

And then hit Ctrl-C it's fine. It only breaks out of the code when I hit it a second time when the line is clear.

If I do setInterval("for (var i=0;i<10000;i++);",100) it'll break out first time around though, because the function has taken a long time to execute and it thinks you want to debug it.

It's a hard thing to get right - ideally if you've done something that's spamming the console with text or is stopped, Ctrl-C needs to break out of it... But then it's also frustrating to accidentally kill one of your tasks.

If there's anything I can do to make it a bit more intuitive, it'd be worth it.

edit: You'd need at least 1v81 though, I changed the logic quite recently.