Unconsistent command-line parsing in case of UTF-8 quoted arguments

[Brian Inglis]

On 2020-10-07 18:59, Eliot Moss wrote:
> I think what we mean is that, under Windows cmd, some things the shell does for
> you under Linux and Cygwin will not have been done.  For example, there is
> "glob" expansion of filenames.  If I write *.txt under bash, it gets expanded to
> a space-separated list of names of files that match that pattern.  This happens
> _before_ calling my program.  If the program is run from Windows cmd.exe, the
> program will receive an argument *.txt, and it will have to do the "globbing"
> itself.  Etc.

That's handled automatically by the Cygwin program startup command line parser
if it is not passed a "Cygwin" command line: that avoids the startup expanding
quoted args that contain wildcards passed from another Cygwin program or shell.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]