Don't use single quotes as quotes in command-line parsing on windows?

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gordon Tyler wrote:
> On 11/7/2009 11:19 AM, John Arbash Meinel wrote:
>> So the point is that it doesn't have to be interpreted that way. I've
>> stayed out of the debate for a bit to see what responses we would get.
>>
>> Obviously I feel that "bzr foo 'ab cd'" should be treated as a single
>> string as it does elsewhere (otherwise I wouldn't have implemented it
>> that way.)
> 
> As I said on the merge proposal, the shell is responsible for quoting.
> The tool shouldn't be implementing it.
> 
> Ciao,
> Gordon
> 

The shell is also responsible for globbing on most systems, and Windows
does not implement it at all.

As such, we work around limitations in the system, and do it ourselves.
To what degree should we do that?

To date, we *didn't* and let the shell take care of most of it, except
for 'bzr add'. People where unhappy with that situation.

So what is a better all-around situation? I felt that implementing a
POSIX style interface would be more comfortable for just about anyone
who was comfortable using a command line.

I'm willing to compromise. Certainly this isn't "you get globs and
quoting, or you get nothing". We can "get globs" and not change the
quoting rules. Though probably there will be some subtle aspects of
"CommandLineToArgv" that doesn't get implemented properly.

I *do* want this issue somewhat resolved before release 2.1.0b3, which
I'd like to do early next week (like Monday). The fact that we are
sprinting next week and I'm currently stuck in a hotel room because a
flight delay made me miss the 1 cross-pacific flight is the only reason
I'm responding right now...

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkr1pCEACgkQJdeBCYSNAAO/JACgnfVSB5oQf1T42MwWMNTZzgVR
V5YAn2F95hZqJScPiGbbAjpcuh4yPd6R
=cBKI
-----END PGP SIGNATURE-----