Re: Unwanted case-insensivity in file name globbing

2015-11-10 Thread Ken Brown

On 11/10/2015 10:44 AM, Paul wrote:

Jan Bruun Andersen  jabba.dk> wrote:
| 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   ntfsbinary,posix=1,user 0
0
| none/   cygdrivebinary,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).

Thanks, Jan.  I was actually looking at that page, and totally glossed
over the posix switch.  Will try it (the machine is elsewhere).


And don't forget about the registry setting you need in order to turn on 
case sensitivity:



https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive

Ken


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



Re: Unwanted case-insensivity in file name globbing

2015-11-10 Thread Paul
Jan Bruun Andersen  jabba.dk> wrote:
| 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   ntfsbinary,posix=1,user 0 
0
| none/   cygdrivebinary,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).

Thanks, Jan.  I was actually looking at that page, and totally glossed
over the posix switch.  Will try it (the machine is elsewhere).

I realize that cygdrive maps all the letter drives, but I'm trying to
cut down on the typed text.


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



Re: Unwanted case-insensivity in file name globbing

2015-11-10 Thread Paul
Ken Brown  cornell.edu> wrote:
> ...don't forget about the registry setting you need in order to turn
> on case sensitivity:
> 
> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-
casesensitive

That's OK, I just need case-insensitive file globbing.  I don't want
to mess with the actual case sensitivity in Win 7 cuz who knows
consequences (human or software) can result.  Besides, I don't have
permissions to change the registry, though I appreciate the awareness.


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



Re: Unwanted case-insensivity in file name globbing

2015-11-10 Thread Jan Bruun Andersen
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   ntfsbinary,posix=1,user 0 0
none/   cygdrivebinary,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  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



Unwanted case-insensivity in file name globbing

2015-11-09 Thread Paul
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