TCC /S switch observations

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Aug 23, 2010
I'm mostly using TCC to write wrappers, and I was looking for ways to avoid constant "ON BREAK QUIT" / "ON BEAK REM" in my scripts.
The /S switch looked promising at first, but then I've discovered that some applications started from shell with this switch enabled lose ability to receive Ctrl+C completely. Namely PHP interpreter can't be interrupted by ^C anymore, but, let's say, Cygwin tools run fine.
At the same time, Ctrl+Break may cause parent TCC to terminate, even if child process is still running. I.e. bash -i will still run, but parent TCC will die, falling down to enclosing console process, if any, leaving both hardly operable.
Last edited: