Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 25 Jan 2001 11:00:35 -0500 From: Ashok Vadekar To: cygwin AT cygwin DOT com Subject: Case discrimination Message-ID: <20010125110035.E20263@volta.certicom.com> Reply-To: avadekar AT certicom DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i I looked at the FAQ for case insensitivity of bash, and tried the recommended shopt -s nocaseglob but it doesn't seem to do what I expected. CD'ed to a directory containing the files "file1" and "File2", I was hoping that typing "ls f" would result in expansion only up to the "e", and a further would present a list of the two files. It did not; instead, I got a fully expanded "file1". Have I got something else wrong, or does the shopt option not do what I was expecting. If not, is there another method of obtaining this behaviour? A related problem, I would like find to perform mixed case matches. I have many SDKS that I compile under, and some of the annoying ones have header files, etc, in upper case names. Searching for a missing header is more difficult because I have to search twice (if I remember). When I'm looking for objects that I may have built, it's even worse, because the files could be file.o, FILE.O or FILE.o. Any suggestions? -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple