Community

Yup!

bveldkamp wrote:How do you know that?

I've modified %ComSpec% on both the system and user-level and cmd.exe is still being launched.

TextPad does not use %ComSpec%

It appears that I was partially mistaken in that TextPad does not always create a batch file. If "Close DOS window on exit" option is NOT checked, TextPad will create a batch file that uses the PAUSE command to keep the Tool from finishing.

So, I've gotten TextPad to execute 4NT directly ... which ...

I have tried that with unsatisfactory results. Regardless of which command you "define" in the Tools menu, TextPad creates a temporary batch file, in $FileDir that contains the command you ultimately want to execute, its parameters, etc. The batch file is always executed by cmd.exe/command.com ...

I found a poll that asks how important is the ability to configure the command processor that TextPad uses to execute user (or built-in) tools, but I did not see an explanation on how TextPad goes about executing cmd.exe/command.com.

Does it:

1. Determine the OS and launch the command, assuming ...