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
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C8CE652.2050208@swcp.com>
Date: Mon, 11 Mar 2002 10:16:02 -0700
From: Lynn Wilson <lynn AT swcp DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: bash expansion question
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

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.

Thanks.
Lynn




--
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/