From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Ev Drikos <drikosev@gmail.com>
Subject: Re: Incorrect expansion of a program argument that is a special character?
Date: Wed, 21 Jul 2021 09:44:51 -0600 [thread overview]
Message-ID: <45070587-e176-3692-2f4d-cfc6275c05a7@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAK5_-8oS-CNCFqL6bqn3YgdnDF4ALq6tn3Z5_AzBEH-P3ai1yQ@mail.gmail.com>
On 2021-07-21 05:42, Ev Drikos via Cygwin wrote:
> When I run the program below from my home directory in a PowerShell
> Console (Windows 8-1) I've to use an extra backslash character as
> shown below or the star is expanded. Which happens only when the
> program has been compiled in Cygwin.
>
> Is this a bug or a known feature?
It's a feature which emulates the argument expansions normally performed
by shells under Unix like systems.
If a Cygwin program is not run from a Cygwin shell, then the Cygwin
program startup argument parsing obeys the quoting rules and performs
the argument expansions which running from a Cygwin shell would normally
perform, so the program sees the same arguments as running from a Cygwin
shell would generate.
Run "info bash 'pattern matching'" then press u (Up) and repeat to see
other argument expansions and processing performed; tab and press Enter
to view Topics; press q to Quit.
--
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.]
prev parent reply other threads:[~2021-07-21 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 11:42 Ev Drikos
2021-07-21 12:18 ` Russell VT
[not found] ` <CAK5_-8oOKuSQd35f2KF=q7Xy5mMQkukEUJa_dja+1WtHUGMcRQ@mail.gmail.com>
2021-07-21 14:21 ` Fwd: " Ev Drikos
2021-07-21 15:44 ` Brian Inglis [this message]
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=45070587-e176-3692-2f4d-cfc6275c05a7@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=drikosev@gmail.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).