On May 27 16:36, Edward McGuire wrote:
This note:
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
warns that you cannot have two filenames in the same directory that
differ only by case, because of NTFS semantics.
No, it does not. *sigh*
I'm not a native
On Sat, May 28, 2011 at 09:50:22AM +0200, Corinna Vinschen wrote:
Did I make myself clear now?
Yep. Perfectly.
I think the discussion prior to your explication brings new meaning to
the term case insensitivity.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ:
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
On May 27 11:53, Lee D. Rothstein wrote:
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.
So
* Lee D. Rothstein (Fri, 27 May 2011 11:53:16 -0400)
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.
This has nothing to do with Cygwin. You are (still[1]) confusing
On Fri, May 27, 2011 at 12:38, Thorsten Kampe
thors...@thorstenkampe.de wrote:
This has nothing to do with Cygwin. You are (still[1]) confusing
Cygwin and your shell. You would hugely benefit from gaining some
basic knowledge about the tools you've been using since 1979.
Your transcript was
* Edward McGuire (Fri, 27 May 2011 16:36:06 -0500)
The globbing is not where the confusion lies. This globbing:
$ ls xwin*
ls: cannot access xwin*: No such file or directory
works as expected and did not confuse anybody.
Lee begs to differ: Globbing is case sensitive [while ...]. And, you
7 matches
Mail list logo
