WAD CDD not working as per help

Mar 20, 2009
35
0
#1
I was using CDD in TC19 build 37. It didn't work as advertised. CDD with no argument gave and error and when using :[name] the /t and /to switches did not change the file explorer directory
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,703
47
Albuquerque, NM
prospero.unm.edu
#2
Do you mean that you're running TCC/LE (the free shell) inside Take Command (the GUI)?

If so, I would not expect /T and /TO to work. Those require backdoor communication between TCC and Take Command, which only works when both are of the same version.

I don't know what CDD with no arguments would give an error; is it possible that you have an alias defined for CDD?
 
Mar 20, 2009
35
0
#4
This is the full purchased TCC as below:

TCC 19.02.37 x64 Windows 10 [Version 6.3.10586]
TCC Build 37 Windows 10 Build 10586
/T and /TO work on non : directories and cd with no arguments works.
 

rconn

Administrator
Staff member
May 14, 2008
10,746
97
#7
Ah, CDD was aliased to cdd/n blank directory and /t work but /to didn't when I removed the alias
/T and /TO were not intended to be used in combination with the :directory syntax. Not that it's impossible to do; but it wasn't done in the initial implementation.

I've added it to the suggestion list for a future build.