Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

On Sat, May 28, 2011 at 09:50:22AM +0200, Corinna Vinschen wrote: >Did I make myself clear now? Yep. Perfectly. I think the discussion prior to your explication brings new meaning to the term "case insensitivity". cgf -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

On May 27 16:36, Edward McGuire wrote: > This note: > > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive > > warns that you cannot have two filenames in the same directory that > differ only by case, because of NTFS semantics. No, it does not. *sigh* I'm not a na

Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

* Edward McGuire (Fri, 27 May 2011 16:36:06 -0500) > The globbing is not where the confusion lies. This globbing: > > $ ls xwin* > ls: cannot access xwin*: No such file or directory > > works as expected and did not confuse anybody. Lee begs to differ: "Globbing is case sensitive [while ...]. An

Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

On Fri, May 27, 2011 at 12:38, Thorsten Kampe wrote: > This has nothing to do with Cygwin. You are (still[1]) confusing > Cygwin and your shell. You would hugely benefit from gaining some > basic knowledge about the tools you've been using since 1979. > > Your transcript was done in a shell called

Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

* Lee D. Rothstein (Fri, 27 May 2011 11:53:16 -0400) > Globbing is case sensitive while full command name invocation/full > filename use is not. And, you may never have been confused by that, > but I maintain it's very confusing. This has nothing to do with Cygwin. You are (still[1]) confusing Cyg

Re: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

On May 27 11:53, Lee D. Rothstein wrote: > > You got that wrong. The CYGWIN=glob:... option only affects how > > globbing is performed on the command line arguments if the Cygwin > > process has been started from a native Windows process. Full stop. > > I acknowledged *my* MISTAKE. I do so again.

File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

> You got that wrong. The CYGWIN=glob:... option only affects how > globbing is performed on the command line arguments if the Cygwin > process has been started from a native Windows process. Full stop. I acknowledged *my* MISTAKE. I do so again. > Now, actual filename case sensitivity is an en

Re: file name case sensitivity

Gerald S. Williams wrote: [snip] But as I said, this is OT for Cygwin. Even if it is added to Cygwin, it will almost certainly not be the default behavior. But for people like me trying to maintain Cygwin versions of Unix projects, it could be a real boon. Indeed. In my case, it would require modi

RE: file name case sensitivity

Sorry this is getting a bit OT... Shankar Unni wrote: > Very interesting. Once you do create such files [...], will regular > Windows programs be able to even look at that directory? Or will > they choke on those names [...] ? Obviously, you need to do something special to get at the files or the

Re: file name case sensitivity

Gerald S. Williams wrote: As you may have guessed, I've been working on this problem recently. I just put a request into SourceForge to create a new project: a library I've been calling CaseWise. It's only for Windows NT/2000/XP since it uses the Native API, but I'm hoping to get Cygwin to use it

RE: file name case sensitivity

Shankar Unni wrote: > > Yes, but in my opinion it could be of use to John Williams because he > > wanted to "case sensitivity in filenames under Cygwin". > > No, it won't work, because if you remember, he said that he had files > with the same name but different case *in the same directory*. Th

Re: file name case sensitivity

Shankar Unni wrote: Thorsten Kampe wrote: Yes, but in my opinion it could be of use to John Williams because he wanted to "case sensitivity in filenames under Cygwin". No, it won't work, because if you remember, he said that he had files with the same name but different case *in the same direc

Re: file name case sensitivity

Thorsten Kampe wrote: Yes, but in my opinion it could be of use to John Williams because he wanted to "case sensitivity in filenames under Cygwin". No, it won't work, because if you remember, he said that he had files with the same name but different case *in the same directory*. This expressl

Re: file name case sensitivity

On Tue, Feb 25, 2003 at 12:59:21PM +0100, Thorsten Kampe wrote: > * Corinna Vinschen (03-02-25 12:51 +0100) > > - Therefore it only fakes case insensitivity in the API so it's > > reliability is restricted. > > Yes, but in my opinion it could be of use to John Williams because he > wanted to "c

Re: file name case sensitivity

* Corinna Vinschen (03-02-25 12:51 +0100) > On Tue, Feb 25, 2003 at 12:42:02PM +0100, Thorsten Kampe wrote: >> * Corinna Vinschen (03-02-25 12:20 +0100) >>> On Tue, Feb 25, 2003 at 11:09:46AM +0100, Thorsten Kampe wrote: * Christopher Faylor (03-02-25 06:06 +0100) > On Tue, Feb 25, 2003 at

Re: file name case sensitivity

On Tue, Feb 25, 2003 at 12:42:02PM +0100, Thorsten Kampe wrote: > * Corinna Vinschen (03-02-25 12:20 +0100) > > On Tue, Feb 25, 2003 at 11:09:46AM +0100, Thorsten Kampe wrote: > >> * Christopher Faylor (03-02-25 06:06 +0100) > >>> On Tue, Feb 25, 2003 at 02:48:05PM +1000, John Williams wrote: > >>>

Re: file name case sensitivity

* Corinna Vinschen (03-02-25 12:20 +0100) > On Tue, Feb 25, 2003 at 11:09:46AM +0100, Thorsten Kampe wrote: >> * Christopher Faylor (03-02-25 06:06 +0100) >>> On Tue, Feb 25, 2003 at 02:48:05PM +1000, John Williams wrote: Is there a way to enable case sensitivity in filenames under Cygwin? >>>

Re: file name case sensitivity

On Tue, Feb 25, 2003 at 11:09:46AM +0100, Thorsten Kampe wrote: > * Christopher Faylor (03-02-25 06:06 +0100) > > On Tue, Feb 25, 2003 at 02:48:05PM +1000, John Williams wrote: > >>Is there a way to enable case sensitivity in filenames under Cygwin? > > > > No there isn't. Sorry. > > What about

Re: file name case sensitivity

* Christopher Faylor (03-02-25 06:06 +0100) > On Tue, Feb 25, 2003 at 02:48:05PM +1000, John Williams wrote: >>Is there a way to enable case sensitivity in filenames under Cygwin? > > No there isn't. Sorry. What about "SET CYGWIN=check_case:strict"? Thorsten -- Content-Type: text/explicit; ch

Re: file name case sensitivity

Hi Elfyn, No. You can use the check_case option in the CYGWIN environment variable, but that'll only get you half way to what you want. Take a look at () to see how it works and how to use it. Thanks for that. As you predict, check_case can't

Re: file name case sensitivity

On Tue, Feb 25, 2003 at 02:48:05PM +1000, John Williams wrote: >Is there a way to enable case sensitivity in filenames under Cygwin? No there isn't. Sorry. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation:

Re: file name case sensitivity

> I'm building a version of uClinux under Cygwin, and for some reason > there are a few places where files exist _in the same directory_ having > identical names but differences in capitalisation. > > For example, /include/linux/netfilter/ipv4/ contains files called > ipt_dscp.h and ipt_DSCP.h . T

file name case sensitivity

Hi folks, I see the thread earlier today about this re: gcc - I have a similar question, but not strictly within the context of gcc. I'm building a version of uClinux under Cygwin, and for some reason there are a few places where files exist _in the same directory_ having identical names but d