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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 15 Aug 2002 19:39:58 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Why does ls command sometimes case sensitively misbehave? In-Reply-To: <005401c244b4$33f68070$1b0a0a0a@phoenix> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 15 Aug 2002, Geoffrey Scheller wrote: > Why is ls doing this? Other commands, like vi, also show > this behavior: > > $ touch foo > > $ ls > foo > > $ ls foo > foo > > $ ls FoO > FoO > > $ ls fo* > foo > > $ ls Fo* > ls: Fo*: No such file or directory > > $ bash --version > GNU bash, version 2.05b.0(2)-release (i686-pc-cygwin) > Copyright (C) 2002 Free Software Foundation, Inc. > > Cygwin DLL version 1.3.12-2 > > I run Cygwin on Windows XP Professional. > > Thanks, > Geoffrey What you're seeing is the behavior of the shell's filename globbing, not of ls or vi. What is the value of your CYGWIN environment variable? Does it contain "check_case:"? Does it contain "glob" or "noglob" (although that, IIRC, is only for command shell windows)? What are the options of bash itself (`set | grep SHELLOPTS`)? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! It took the computational power of three Commodore 64s to fly to the moon. It takes a 486 to run Windows 95. Something is wrong here. -- SC sig file -- 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/