Backslashes in command arguments

I realized this later. That you can’t have different rules for different arguments because you need to tokenize the whole string using one set of rules.

So how about this instead? We just implement a cmd.exe compatible tokenizer, and then you have a setting like “setting set tokenizer [cmd/bash]”, and the default on windows is cmd, and the default otherwise is bash. Where the current implementation of Args::SetCommandString is considered the bash implementation.

That would be okay too, but I would definitely NOT call it "bash" since we are by no means trying to emulate the bash shell's tokenization. Probably something like "unix" vrs. "windows" would be better. The settings help can then describe the differences between the two tokenizers.

Jim