MVV wrote:I think you can allow parameter:
It will work only with new TC versions, old ones will simply report an error or do nothing (like now).
??? It simply opens archive "a archive.zip" in the root.
I noticed different behavior between "cd" on TC's command line and "cd" as button command.
Breadcrumb bar shows "c:\a archive.zip" when the command mentioned above is executed on the command line.
Breadcrumb bar shows "c:\/a archive.zip\*.*" when the command mentioned above is executed as button command. When you edit this path (cm_EditPath) the path is displayed as "c:\/a archive.zip/".
It seems that:
cd on command line: "/" is replaced by "" for local file system
cd as button command: "/" is not replaced for local file system
ghisler(Author) wrote:Sorry, currently not possible - cd supports path with spaces without using double quotes, and "somefile.zip /A" is a valid subdir.
I tried to make such subdir. You need to make subdir "A" in subdir "somefile.zip ". In Windows XP I can't create folders with a trailing space in the name
(*). In a unix shell i was able to create such folder (can't with TC's ftp client). The command "cd somefile.zip /A" works when the source panel shows the unix folders in TC's ftp client.
Again I noticed different behavior between "cd" on TC's command line and "cd" as button command when TC's ftp client is active.
"cd folder" on command line: works as expected.
"cd folder" as button command: A "Drive not found" error is displayed. Strangely enough "cd folder/subfolder" or "cd folder/" works OK.
Certainly there are things to consider when adding parameter /A to the cd command. Perhaps TC should first treat it as part of the folder name. If the folder does not exist, treat it as a parameter. Another way and much simpler would be to simply add an new command, e.g. "cda".
(*) I can create folders with a trailing space in the name, but did not know how.