I browsed for a folder using whatever functionality Touch provides (can’t remember) the results were: S:\Jobs\Show_Template\Show
which Touch, recognizing that there was such a variable ($jTop) basically returned as $jTop.
Then I used filetype(“$thatfolder”) to make sure the folder was indeed a folder… and I got “error” as a result, because filetype does not understand backslashes. So I had to type the full path, with forward slashes, instead of using your browser.
basically anything in Touch that relates to files - IMHO - should be able to take either forward or backslashes, otherwise we’re left with bumping into these behavioral inconsistencies! (like the folder returned by your file browser has backslashes, but your software functions don’t understand them)
Backslashes are stuck being used as escape characters though. I’d be interested in know how you got a path with backslashes though as I agree that’s a bug.
I’m using the “filechooser” command to bring up a browser.
what I get back is $jTop - which happens to be - in this case - one of my environment variables which I use in DOS before calling Touch.
So I guess it’s a bug? Meaning, if I browse to a folder that I have no env vars for, I see forward slashes. So I guess the matching of the path to my env vars (which is really cool btw) happens before the conversion to forward slashes?
To follow up on this, if we assume $jTop has backslashes, then maybe the solution is to not do the auto-variable substitution when the variable has backslashes?