TC uses noclose.pif when you press Shift+Enter for keeping the shell window open, so you can read the output of executed commands or batches.
But this shell is no longer active and allows no further working with it.
In WinXP you can use cmd.exe /k what keeps the shell open and active.
My suggestion for taking advantage of this feature within TC is adding 2 new settings to wincmd.ini.
They are meant to modify what Shift+Enter in TC does:
UseNoclosePif=(1/0)
=1 means TC uses noclose.pif from %WinDir% (current behavior). This would be standard in TC and the choice for Win9x users. Novices would not have to bother with it.
=0 is for more experienced users of WinXP/2k/NT and means TC ignores noclose.pif and is forced to execute the command with a preceded {VarText} defined in the 2nd setting:
ShiftEnterLine={VarText}
{VarText} could be cmd /k (or %comspec% /k or d:\4NT\4NT.exe /c).
For example: When you type in TC command line DoThis.bat and press Shift+Enter, TC would execute cmd /k DoThis.bat.
With this realized in TC, WinXP/2k/NT users would have the chance to get rid of this obsolete noclose.pif while TC would be downwards compatible to Win9x.
So please vote for it here! Post your comments there (thread in english forum).
Should TC make "cmd /k" usable with Shift+Enter?
Moderators: white, Hacker, petermad, Stefan2
[/mod]