Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 20 Oct 2002 12:14:10 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: bash -c Message-ID: <20021020161410.GA13094@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <5.1.0.14.2.20021020084313.02f91a40@pop3.cris.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/