Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	Tue, 28 Jun 2005 15:50:22 +0100 (BST)
From:	Nikhil Nair <nnair AT pobox DOT com>
X-X-Sender:	nn201 AT dsl-212-23-31-41 DOT zen DOT co DOT uk
To:	cygwin AT cygwin DOT com
Subject:	RE: LS and spaces in path names (the xth)
In-Reply-To:	<SERRANOVypkj9KYinql0000024b@SERRANO.CAM.ARTIMI.COM>
Message-ID:	<Pine.LNX.4.58.0506281538590.11829@dsl-212-23-31-41.zen.co.uk>
References:	<SERRANOVypkj9KYinql0000024b AT SERRANO DOT CAM DOT ARTIMI DOT COM>
MIME-Version:	1.0
X-IsSubscribed:	yes

Hi,

Just a quick observation - but first an apology: I haven't read the
thread, as I've only just subscribed, so this may have already been said.

I'm a bit surprised by this wildcard behaviour, as I would have assumed
"CD 1..." would have been picked up by "CD *".

I'd suggest that this is a bash issue, not one with ls: I get similar
behaviour if I use echo rather than ls.  I presume, when you use ls, it's
bash's job to expand wildcards in the command line before they're passed
to ls...

Cheers,

Nikhil.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -