> The problem is that the glob() function is exported from the > DLL. I don't > know if its operation should be under the control of the > CYGWIN environment > variable when it is called by the program directly. I don't > think it should > be actually. I agree. I've made the change and attached new patches. > I'd appreciate it if you would test that glob's operation > when called from > a program is unchanged, too. Source to the program I used to test is attached. So, for those of you just joining us, adding "glob" to the CYGWIN environment variable enables case-sensitive globbing for arguments passed on the command line when the program is called from a Windows shell. With the patches, "glob:ignorecase" would make the globbing case-insensitive. Brad Town -------------- next part -------------- A non-text attachment was scrubbed... Name: dcrt0.cc.patch Type: text/x-diff Size: 450 bytes Desc: not available URL: <http://cygwin.com/pipermail/cygwin/attachments/20001109/1c4adfee/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: environ.cc.patch Type: text/x-diff Size: 1559 bytes Desc: not available URL: <http://cygwin.com/pipermail/cygwin/attachments/20001109/1c4adfee/attachment-0001.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: glob.c.patch Type: text/x-diff Size: 1680 bytes Desc: not available URL: <http://cygwin.com/pipermail/cygwin/attachments/20001109/1c4adfee/attachment-0002.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: globtest.cc Type: text/x-c Size: 838 bytes Desc: not available URL: <http://cygwin.com/pipermail/cygwin/attachments/20001109/1c4adfee/attachment-0003.bin>