Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20001102195913.00b67c90@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Thu, 02 Nov 2000 19:59:57 -0500
To:	cygwin AT sources DOT redhat DOT com
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: Cygnus question
In-Reply-To:	<20001102190837.J15890@redhat.com>
References:	<50028CAE26D1D3118C7F00A0CC50D6256A9344 AT EMWARESERVER>
	<50028CAE26D1D3118C7F00A0CC50D6256A9344 AT EMWARESERVER>
Mime-Version:	1.0

At 07:08 PM 11/2/2000, Christopher Faylor wrote:
>On Thu, Nov 02, 2000 at 04:50:02PM -0700, Scott Carter wrote:
> >I'm not a unix expert, nor a Windows expert, but I don't think David's
> >statements are all  correct. In unix, as I understand it (and as David
> >stated), it is the shell (bash, csh, ksh, ...) that does the filename
> >expansion on the b* argument in 
> >ls b*
> >The shell passes that expansion to ls on the command line (unless the
> >expansion is empty, in which case the shell just passes the b*).
> >
> >If you have cygwin installed on a WinNT machine (with the cygwin bin
> >directory in the PATH), you can run the cygwin ls command from the WinNT
> >command prompt, and it works, the same as it does from a cygwin bash prompt.
> >But I'm pretty sure that the WinNT shell (cmd.exe) does NOT expand b*.  If
> >that is true, ls must read the b* from the command line and (likely) pass it
> >to a function which does the expansion. And I suspect that the function is
> >located in the cygwin1.dll, and that it, in turn, calls a windows function,
> >which is case insensitive. If that is true, the cygwin function would have
> >to do extra work to force case sensitivity. [semi-educated speculation]
> >
> >So it seems to me that it would be possible to make ls case insensitive in
> >cygwin. 
> >
> >Whether or not it's a good idea, and how easily it could be done, is a
> >different issue.
>
>Cygwin does wildcard translation on the command line when a program is
>run directly from a Windows command shell.  It does this prior to starting
>the program just like bash.
>
>There are no facilities in cygwin for case insensitive globbing currently
>and I have no plans or desires to add this.  If someone is interested
>(hah) in providing a patch, I'll gladly consider it.
   ^^^^
   Hope you didn't bust a gut on that one Chris!;-)


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


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -