Firstly,
Oops - I retested and it does work with quotes, but not with the comment on the line.
I thought I had deleted this when testing.
> > That "fixes" it, but I still regard this as a bug, because it
> worked
> > until recently, and I will have to change all my history.
>
> I wasn't suggesting this was the fix (although some folks seem to
> mistakenly assume quotes are required for prompts other than
> command lines), but merely try to gather more data.
Kim, I wasn't suggesting that you thought this was the fix, merely suggesting that
meant I would have to change all my history.
> Is this exactly the string that fails: "D:\CPP\TFC for
> Windows\TFCSource.zls" ?
The original was:-
"D:\CPP\TFC for Windows\TFCSource.zls" ; Tag files for TFC for Windows source
I now have lots of other permutations in my history, and both
"D:\CPP\TFC for Windows\TFCSource.zls"
D:\CPP\TFC for Windows\TFCSource.zls
work.
This still represents a change from 2.1.120, and I will have to edit a lot of my history.
I was relying on the fact that passing a quoted string to the file open API works, as it ignores other parameters on the line - which obviously doesn't work without quotes.
As I was using an undocumented feature I withdraw the bug report, although I found this useful.
In most of my own code, if I find a leading quote I isolate the contents of the quoted string, and pass just this to the relevant API.