This is the mail archive of the
mailing list for the Cygwin project.
Re: Why does ls command sometimes case sensitively misbehave?
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: cygwin at cygwin dot com
- Date: Thu, 15 Aug 2002 19:39:58 -0400 (EDT)
- Subject: Re: Why does ls command sometimes case sensitively misbehave?
- Reply-to: cygwin at cygwin dot com
On Thu, 15 Aug 2002, Geoffrey Scheller wrote:
> Why is ls doing this? Other commands, like vi, also show
> this behavior:
> $ touch foo
> $ ls
> $ ls foo
> $ ls FoO
> $ ls fo*
> $ 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.
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:<smth>"? 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`)?
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.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