Allow the use of command processors other than "command
Posted: 2012-07-07, 12:30 UTC
As best as I can determine, it seems that TC has hard-wired the command processor used by the command-line to "command". For the benefit of those, like myself, who use alternative command processors, I would like to recommend that TC use the contents of the environment variable "comspec" to determine the name and path to the command processor. Alternatively, provide a configuration option to allow the user to specify the command-processor to use.
In addition, there should be a way to configure the string which is prefixed to the command in the command-line when SHIFT-ENTER is used, in case the alternative command-processor does not support /C.
In addition, there should be a way to configure the string which is prefixed to the command in the command-line when SHIFT-ENTER is used, in case the alternative command-processor does not support /C.