Quote:
PvK said:
the MS docs I found that mentioned the situation didn't explain that.
|
I think it's a bug. If the quote marks appear before the disk ID, the shell interprets the entire commandline as tho it was in quotes, regardless of the location of closing quote marks. I was testing the Windohs catgod, and found that playing with the quote marks changed the error from "invalid argument" to "file not found", which suggested a misparse somewhere.