> 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 entirely different issue.
> This is handled by a registry setting, the ability of the underlying
> filesystems to handle filenames case sesitive, and the settings of
> the Cygwin mount point:
>
>
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
> http://cygwin.com/cygwin-ug-net/using.html#mount-table
I acknowledged this point as well in my initial post, and why I reject it.
The point remains:
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. I'm
not asking that it be "fixed", I'm asking that it be carefully
documented, and I'm not asking anyone but me to do it. If it is
so documented, I missed it. And, I read and reread that part of
the manual before posting both times.
I offered an example session transcript that made that perfectly
clear, and I am willing to write that up however you want it.
Thus far, you've made clear you don't want it. No further replies
will be required if my last "read" is correct.
--
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
