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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 28 Jun 2005 13:33:52 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Nikhil Nair cc: cygwin AT cygwin DOT com Subject: RE: LS and spaces in path names (the xth) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 28 Jun 2005, Nikhil Nair wrote: > 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... Not if they're quoted. As others said, 'ls "CD "*' works as expected. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- 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/