- Jan
- 1,189
- 25
If I closing the ConPTY tab, it closes also TCMD (it took some seconds or so (longer than a normal exit)).
PS: Tested without any PlugIns.
PS: Tested without any PlugIns.
By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!Yes. I've commented on it recently in another thread (or two). For example, after start /tab /pgm "d:\tc36\tcc.exe", EXIT, in the tab where you issued that command, causes both tabs and TCMD to terminate.Not reproducible here.
Anybody else seeing this?
I just tested this sequence of instructions on my system (v36.50.71) and what you described above will occur IF I have only one tab with TCC running in TCMD. However, if I have other tabs active (such as Cygwin, MSYS, FAR, etc.) in addition to TCC, then exiting the parent tab will ALSO kill the child tab (the new instance of tcc.exe just invoked), but will not kill the other tabs and will not terminate TCMD.Yes. I've commented on it recently in another thread (or two). For example, after start /tab /pgm "d:\tc36\tcc.exe", EXIT, in the tab where you issued that command, causes both tabs and TCMD to terminate.
start /tab to open a new tab. I then when back to the original tab and ran the exit command. There was no problem; the new tab remained open. I ran tasklist to make sure that there were no TCC sessions I didn't know about.TCC Version: 36.50.71TCMD Tab: YesConPTY: YesConsole Type: PseudoConsoleWindowElevated: NoTCC Version: 36.50.71TCMD Tab: YesConPTY: YesConsole Type: ConsoleWindowClassElevated: No