Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <4.3.1.2.20020311123358.033d2b88@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 11 Mar 2002 12:34:35 -0500 To: Lynn Wilson , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: bash expansion question In-Reply-To: <3C8CE652.2050208@swcp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 12:16 PM 3/11/2002, Lynn Wilson wrote: >The man page for bash says: >Enclosing characters in single quotes preserves the lit- >eral value of each character within the quotes. A single >quote may not occur between single quotes, even when pre- >ceded by a backslash. > >If I write the following bash script( test.bash ): >#!/usr/bin/bash >echo Argument is $1 > >If I execute this script in a directory that does NOT constain >any perl (*.pl) files: > >test.bash '*.pl' >I get as expected: Argument is *.pl > >However if there IS a perl file present I get: >Argument is filename.pl > >BTW, I get exactly the same behavior if I use double quotes. >Am I missing something here? I need to pass a literal pattern that >may contain wildcard characters into a bash script and not have the >shell expand it. This really isn't related to Cygwin. It's a shell question. I suggest you take it to the appropriate forum. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/