> I've showed this session as example of cmd.exe behavior and maybe as possible source for extending test suite. I'm still trying to figure out how your new command-line parsing may impact on qsubprocess and bencoded command-line.
If qbzr wraps everything in "" as most programs do, then I think
everything will be ok. It may need to do:
args = [" + arg.replace('"', '\\"') + " for arg in args]
Which generally wraps any argument in "" and then escapes any embedded
quotes.
With that syntax, bzr should be the same as the standard
CommandLineToArgv parser. (caveat bugs)
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
...
> I've showed this session as example of cmd.exe behavior and maybe as possible source for extending test suite. I'm still trying to figure out how your new command-line parsing may impact on qsubprocess and bencoded command-line.
If qbzr wraps everything in "" as most programs do, then I think
everything will be ok. It may need to do:
args = [" + arg.replace('"', '\\"') + " for arg in args]
Which generally wraps any argument in "" and then escapes any embedded
quotes.
With that syntax, bzr should be the same as the standard
CommandLineToArgv parser. (caveat bugs)
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEUEARECAAYFAkr 2Eo8ACgkQJdeBCY SNAANjXgCgiu3cH X0sblh0hENKO0u/ nzm6 U8BuMLN/ Q5CcMDj8=
Bo0AkwVm8qdMNqf
=9Dql
-----END PGP SIGNATURE-----