Re: Unwanted case-insensivity in file name globbing

[Jan Bruun Andersen <jan_bruun_andersen@jabba.dk>]

Seems overly complicated for me. My current fstab looks like this:

# /etc/fstab
#
#    This file is read once by the first process in a Cygwin process tree.
#    To pick up changes, restart all Cygwin processes.  For a description
#    see https://cygwin.com/cygwin-ug-net/using.html#mount-table

# Device-       Mount-          FS-type         Options                 Ignored
# name          point
# ------------- --------------- ---------------
----------------------- --------------------

C:/Users        /home           ntfs            binary,posix=1,user     0 0
none            /               cygdrive        binary,posix=0,user     0 0

If I remember correctly the cygdrive thing is what automatically maps
all my C:. D:, E:, etc drives to /C, /D, E and so on.

The magic with posix is described here:
https://cygwin.com/cygwin-ug-net/using.html#mount-table

  posix=0   - Switch off case sensitivity for paths under this mount point
     (default for the cygdrive prefix).

  posix=1   - Switch on case sensitivity for paths under this mount point
     (default for all other mount points).

Regards,

On 10 November 2015 at 04:15, Paul <Paul.Domaskis@gmail.com> wrote:
> 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
>

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