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
Reply-To:	Cygwin List <cygwin AT cygwin DOT com>
Message-Id:	<6.1.0.6.0.20041006202208.03fd51e8@pop.prospeed.net>
X-Sender:
Date:	Wed, 06 Oct 2004 20:28:00 -0400
To:	<DFong AT s3graphics DOT com>, <cygwin AT cygwin DOT com>
From:	Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject:	Re: problem with finding case-sensitive filenames when running DOS batch command with bash shell
In-Reply-To:	<D1F33C67F65972439ECA4B6BD0B18E7303725420@exchsg01.s3graphi cs.com>
References:	<D1F33C67F65972439ECA4B6BD0B18E7303725420 AT exchsg01 DOT s3graphics DOT com>
Mime-Version:	1.0

At 02:24 PM 10/6/2004, you wrote:

>Hi,
>
>I'm running cygwin bash shell and have set
>the parameters
>
>~/.bashrc
>
>shopt -s nocaseglob
>
>~/.inputrc
>
>set completion-ignore-case on
>
>but I'm still having problems with running a DOS batch command that will not be case-sensitive.


None of the above affects DOS/cmd.exe/command.com functionality.  It controls
bash/readline functionality.


>x.bat
>dir /s /b filename.txt (I want it to match with name like fileNAME.txt and return filename.txt)
>
>If I run this x.bat under cygwin bash shell
>the return from dir /s /b command is "file not found".


Works fine for me.  The obvious question is, are you in the directory with 
'fileNAME.txt'?


>What else do I need to set in DOS or bash shell environment
>to allow "dir /s /b" to make the directory search for filename to be case-insensitive?


That's a DOS/Windows question, not a Cygwin one.  So it's really off-topic
here.  However, there is no need to "set" anything for Windows to treat
file names in a case insensitive way.  It does that already (and really 
won't treat them any other way at the cmd/command prompt).  Your problem 
must actually be caused by something else on your machine.

--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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 -