Post by TheFeDuke on Feb 13, 2016 1:03:35 GMT -5
I place some code at the end of batch scripts for testing both in a 'DOS Prompt' window or using the RUN primary EDIT command. The script ends with no noise in the Command Prompt and closes the RUN window with just an 'Enter' after viewing output.
[Edited: The original contribution has been generalized in anticipation of updates after v8.3.6022].
[Edited: Some simplification and added handling a window started by double-click]
I cannot contain my question of curiosity. Why does SPFLite use the RUN name in the format: batchname..bat ?
[Edited: The original contribution has been generalized in anticipation of updates after v8.3.6022].
[Edited: Some simplification and added handling a window started by double-click]
:Xit
SetLOCAL EnableDelayedExpansion&Set Clean="%CmdCmdLine:&=Ampersand%"&Set x=%~p0&Set x=!x:\run\=!
For /F "tokens=1-2*" %%C In (%Clean%) Do If /I "%%D" EQU "/C" %ComSpec% /K Echo.Enter 'Exit' to end dbl-clk window...
If "%x%" NEQ "%~p0" (Echo.Press 'Enter' to end SPF RUN window...&Pause>nul&Exit) Else Exit /B
The original code below should not be used after the .dot bug is fixed. [Edited: 8.4.6075 (Mar 15/2016) changed the ..] Set "TILDEn=%~n0" %=== SPFLite RUN filename ends in ..BAT so close Window ===%
If "%TILDEn:~-1%" EQU "." (Echo.Press 'Enter' to end SPF RUN window...&Pause>nul&Exit)
Exit /B %=== End batch script leaving Window open in DOS Prompt ===%
I cannot contain my question of curiosity. Why does SPFLite use the RUN name in the format: batchname..bat ?
