START /K ...

May 20, 2008
12,332
134
Syracuse, NY, USA
If I issue
Code:
start /k dir
I get a new TCC (new console), DIR is executed, and the STARTed TCC hangs around. I figure that's correct behavior.

If I issue
Code:
start /k dir /p
I get a new TCC (new console) with DIR in progress, sitting at the /P prompt If, in that new TCC, I press <Esc> (to end the DIR command) the STARTed TCC exits. That doesn't seem right.
 
BTW, that was a bit of a simplification. I first noticed the behavior with "start /K do forever ..." and Ctrl-C, expecting the DO loop to be terminated, and finding that TCC was terminated.
 

Similar threads