(being interpreted by TCC) with a Ctrl-C, TCC disappears (occasionally "encounters a problem"). IIRC this has been discussed before but I don't remember what came of it.
> If I try to interrupt the Perl script
>
> sleep 10;
>
> (being interpreted by TCC) with a Ctrl-C, TCC disappears (occasionally
> "encounters a problem"). IIRC this has been discussed before but I don't
> remember what came of it.
Nothing became of it -- it's a problem with Perl, not TCC. (Perl
replaces the default TCC break handler with its own, which summarily
terminates the app instead of correctly passing it on to any other break
handlers that may be installed.)
The only workaround is to compile a custom version of Perl with the
offending code fixed.
> If I try to interrupt the Perl script
>
> sleep 10;
>
> (being interpreted by TCC) with a Ctrl-C, TCC disappears
> (occasionally "encounters a problem"). IIRC this has been discussed before but
> I don't remember what came of it.
I managed to kill TCMD recently with only Ctrl-C (not Break) a while ago as well. It was then running an alias and/or batch file using only TCC internal commands.
After I restarted TCMD I could activate the TCC window and attach it so it seems only TCMD and not TCC was killed.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.