using firefox 57.0.2 on windows 10
Just as confirmation, I also see this happen.
I’m wondering if the terminal that is catching the ‘Abort’ is actually aborting, when, in regular terminals it would be ignored (since usually it’s supposed to abort the currently running program). Perhaps the Glitch team can help us here.
this took incredibly long to fix, we’re sorry about it We just deployed the fix! (If your project was running during the deploy, it needs to go to sleep before you can see the fix)
Thank you so much for this.
Great, I can Ctrl+C in the shell now. Now we don’t have to backspace out a command if we change our mind.