By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!Cmd.exe can use wildcards for the cd statement and tccle cannot. This is the reason I continue to use cmd.exe and not tccle. Cmd.exe is free and so is tccle, but tccle cannot use wildcards and cmd exe can. Score one for Microsoft and zero for jpsoft.You can: "TCC (but not TCC/LE) also supports wildcards in the directory names (but not in the drive name). You can control the subdirectory recursion by specifying * or ** in the path. A * will match a single subdirectory level; a ** will match any all subdirectory levels for that pathname. Directory wildcards also support regular expressions."
Cmd.exe can use wildcards for the cd statement and tccle cannot. This is the reason I continue to use cmd.exe and not tccle. Cmd.exe is free and so is tccle, but tccle cannot use wildcards and cmd exe can. Score one for Microsoft and zero for jpsoft.
Cmd.exe can use wildcards for the cd statement and tccle cannot. This is the reason I continue to use cmd.exe and not tccle. Cmd.exe is free and so is tccle, but tccle cannot use wildcards and cmd exe can. Score one for Microsoft and zero for jpsoft.
However, TCC/LE has *always* supported wildcards in CD, just not the blind "maybe I'll change to a random matching directory and maybe I won't" behavior of CMD. Try:
CD r*<F7>