Hi Cygwin team,
Here is a consolidated bug report based on the discussion in recent days which
I'd started under the subject " shell expansion produces e.g. "ls: cannot
access '*.pdf': No such file or directory" in Windows CMD shell, but works okay
in bash " (thread starter
https://cygwin.com/p
Hi Andrey,
(I have no idea what you mean about "top posting".)
`locale` gives the same in CMD as in bash, on this machine as on another
machine on my network where I also checked, which also exhibits the same
globbing problem under Windows CMD:
LANG=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_T
: Sunday, 22 March 2020 20:09
> To: Jay Libove
> Cc: cygwin@cygwin.com
> Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf':
> No such file or directory" in Windows CMD shell, but works okay in
> bash
>
> Is this because cygwin globbing is (by d
okay in bash
Is this because cygwin globbing is (by default) case sensitive? You could set
the CYGWIN environment variable to "glob:ignorecase" to get case-insensitive
behaviour.
Paul
On Sun, 22 Mar 2020 at 17:52, Jay Libove via Cygwin wrote:
>
> I've never seen t
I've never seen this before.
In a Windows CMD shell, Cygwin shell expansion, for example:
ls *.pdf
returns:
ls: cannot access '*.PDF': No such file or directory
(Indeed, any Cygwin shell expansion, when executed from within Windows CMD,
produces this error. See below)
ls *someotherwildcard* (tha
5 matches
Mail list logo