Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sun, 20 Oct 2002 12:14:10 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: bash -c
Message-ID:	<20021020161410.GA13094@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<F49TuAyHsjCGvseE4D300008bf8 AT hotmail DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021020084313 DOT 02f91a40 AT pop3 DOT cris DOT com>
Mime-Version:	1.0
In-Reply-To:	<5.1.0.14.2.20021020084313.02f91a40@pop3.cris.com>
User-Agent:	Mutt/1.5.1i

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/

- Raw text -