> 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 en
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.
* 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 Cyg
On Fri, May 27, 2011 at 12:38, Thorsten Kampe
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 done in a shell called
* 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 ...]. An
5 matches
Mail list logo
