From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Unconsistent command-line parsing in case of UTF-8 quoted arguments
Date: Thu, 8 Oct 2020 00:22:16 -0600 [thread overview]
Message-ID: <06aad40b-5a37-d432-5d43-b46ad7f0a84c@SystematicSw.ab.ca> (raw)
In-Reply-To: <e918356a-be86-1026-4608-ddf05dfa4fab@cs.umass.edu>
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.]
next prev parent reply other threads:[~2020-10-08 6:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 21:40 Jérôme Froissart
2020-10-03 2:22 ` Doug Henderson
2020-10-04 11:18 ` Andrey Repin
2020-10-06 21:36 ` Jérôme Froissart
2020-10-07 1:10 ` Andrey Repin
2020-10-07 22:21 ` Jérôme Froissart
2020-10-11 18:55 ` Andrey Repin
2020-10-07 2:20 ` Brian Inglis
2020-10-07 5:17 ` Thomas Wolff
2020-10-07 23:32 ` Brian Inglis
2020-10-08 0:59 ` Eliot Moss
2020-10-08 6:22 ` Brian Inglis [this message]
2020-10-13 16:30 ` Kaz Kylheku (Cygwin)
2020-10-14 21:47 ` Jérôme Froissart
2020-10-14 22:14 ` Jérôme Froissart
2020-10-15 5:14 ` UTF-8 quoted args passed to program include quotes when run from cmd Brian Inglis
2020-10-19 2:32 ` Unconsistent command-line parsing in case of UTF-8 quoted arguments Kaz Kylheku (Cygwin)
2020-10-13 17:34 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06aad40b-5a37-d432-5d43-b46ad7f0a84c@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).