Cursor dissapears after CTRL-C in mocha --watch

[mcortesi]

It seems mocha hides the cursor during the run but it forgots to enable it again when a SIGINT is sent...

In my script i had to do:

  process.on('SIGINT', function() {
    // show cursor
    console.log("\x1B[?25h");
    process.exit();
  });

[rzane]

Yeah, this has been bothering me for a long time. Here's the equivalent bash:

trap 'echo "\x1B[?25h"' INT

[Munter]

This one has been bothering me a lot as well. I tried to spot what caused it a while ago, but didn't have the time to properly dive into it. It's also a hard issue to write a good test case for, so verifying a fix without regressions is a bit tricky.

PR welcome obviously

[refractalize]

any appetite for just keeping the cursor visible in the first place? Using tmux, it's not obvious which pane is focussed without a cursor - or is that just me?

[Munter]

I think we're not listening to enough signals that might cause an exit, so we don't call cleanup properly. We could try using https://github.com/jtlapp/node-cleanup

[jayjanssen]

Same

[mscharley]

This is happening to me too. Personally, I'm in the same situation as refractalize. I'd be more than happy if there was a flag or something to disable this altogether.

[mscharley]

Yet more alternatives, an NPM script:

"scripts": {
  "fix-cursor": "node -e 'console.log(\"\\x1B[?25h\");'"
}

[glebec]

Or an alias for your ~/.zshrc or bash profile, lol. Thanks @mcortesi & @rzane.

alias showc='echo "\x1B[?25h"' # show cursor after e.g. Mocha has hidden it

[juergba]

closed by #3980

[jedwards1211]

@juergba I'm still seeing this issue in Mocha 8.2.1, it never seems to have gone away
Actually, seems like it might be some subtle issue with spawning mocha with stdio: 'inherit'... 😕 or something else my own scripts are doing with chalk...

Another confusing thing that's happening to me is after I Ctrl-C, when I press the up arrow to go back to the last command, it prints ^[[A instead of showing the command. This even if I use the workaround shown above

Okay nevermind, the issue was whenever running via yarn 1 or my own spawn scripts that fail to pass SIGINT to the child process and wait for it to close.