This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Unwanted case-insensivity in file name globbing


I just replicated my Cygwin setup on Win 7 (64 bits) onto another Win 7 64-
bit machine, including /etc/fstab

   c: /c ntfs binary,posix=0,user,auto
   d: /d ntfs binary,posix=0,user,auto
   e: /e ntfs binary,posix=0,user,auto
   f: /f ntfs binary,posix=0,user,auto
   g: /g ntfs binary,posix=0,user,auto
   i: /i ntfs binary,posix=0,user,auto
   o: /o ntfs binary,posix=0,user,auto
   r: /r ntfs binary,posix=0,user,auto
   s: /s ntfs binary,posix=0,user,auto

So my home directory "~" is "C:\cygwin64\home\My.User.Name".

I noticed that when I issue a command involving a file name pattern, it is 
not case sensitive in that directory.  For example, "ls -d [A-Z]*" will 
return the folder "cat".  Web searching revealed that it could be the bash 
shell option nocaseglob, but I confirmed that in my case, it is not set:

   $ shopt -p nocaseglob

      shopt -u nocaseglob

I am also puzzled by the fact that when I cd to a subdirectory, the 
unwanted case insensivity is no longer present.  I thought that I did 
something wierd in replicating my Cygwin setup, but when I tested my 
original setup on the 1st computer, I found the same selective case 
insensitivity.

What other setting might cause this?  How can I get bonafide Unix behaviour 
in the file name globbing?


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]