On 22/12/2018 9:31 am, Bernd Eckenfels wrote:
Hello,
David:
I don't have an issue with your fix. I just don't understand how the
existing test actually works when the test cases seems to fail at the
command-line for me.
I think the difference between commandlie and testcase is, that the command
line Interpreter might do some additional Interpretation of quotes and the
process builder might transparently wrap Arguments in additional quotes. If I
recall correctly on Windows the launcher does some quite Interpretation, not on
*nix. Maybe ist best to compare the command line of the running process to be
sure all intended cases are tested?
(But for Windows ist not that easy to pass those quotes as theyare removed on
muiltiple Levels – I think tripple quotes might pass through), so supporting
single quotes and also raw drive letter (even when seem uncanonical
interpretation) seems like a good idea.)
I've no idea what's happening. All I know is that syntax that is
supposed to work (not altered by this bug) is not actually working.
It will be interesting to see what happens after this patch is applied.
Thanks,
David
On Linux I would rather expect to generate filenames with single quotes if it
is docmented to look for double quotes only. (I I pass a quoted single Quote to
a command it will be part of the file name on most unix Tools)
Gruss
Bernd
