This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: bash -c

From: Christopher Faylor <cgf at redhat dot com>
To: cygwin at cygwin dot com
Date: Sun, 20 Oct 2002 12:14:10 -0400
Subject: Re: bash -c
References: <F49TuAyHsjCGvseE4D300008bf8@hotmail.com> <5.1.0.14.2.20021020084313.02f91a40@pop3.cris.com>
Reply-to: cygwin at cygwin dot com

On Sun, Oct 20, 2002 at 08:55:53AM -0700, Randall R Schulz wrote:
>I'm not completely well-versed on this detail, but I'm under the impression 
>that the interpretation of "*" is different when a Cygwin command is 
>invoked directly from a Windows CMD.exe. (In a fully Cygwin context, the 
>shell itself handles wildcard expansion, but Cygwin programs have special 
>startup code that's activated when they're launched from a non-Cygwin 
>parent process. That special startup code detects the presence of the 
>wild-card character in the arguments and expands them as CMD.exe would).

In this case, the shell should still be handling the wildcards since they
are quoted.

>Chris F.: Please do write that book!

I'm negotiating as fast as I can.  :-)

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

References:
- bash -c
  - From: g frances
- Re: bash -c
  - From: Randall R Schulz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]