| View previous topic :: View next topic |
| Author |
Message |
RichieTheK Junior Member

Joined: 16 Aug 2008 Posts: 5
|
Posted: Sat Jul 07, 2012 6:30 am Post subject: Allow the use of command processors other than "command |
|
|
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. |
|
| Back to top |
|
 |
MVV Power Member


Joined: 03 Aug 2008 Posts: 4541 Location: Russian Federation
|
|
| Back to top |
|
 |
RichieTheK Junior Member

Joined: 16 Aug 2008 Posts: 5
|
Posted: Sun Jul 08, 2012 4:41 am Post subject: |
|
|
| Thank you, I'll try it. |
|
| Back to top |
|
 |
ghisler(Author) Site Admin


Joined: 04 Feb 2003 Posts: 24621 Location: Switzerland
|
Posted: Mon Jul 09, 2012 9:03 am Post subject: |
|
|
Yes, when you press Shift+Enter, noclose.exe is using cmd.exe and command.com, depending on the Windows version. Enter does use comspec for commands like the dir command. _________________ Author of Total Commander
http://www.ghisler.com |
|
| Back to top |
|
 |
|