DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E1855385E001
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
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
References: <DM5PR13MB087674FC4FC989DE45C41E8ECBF30@DM5PR13MB0876.namprd13.prod.outlook.com>
Message-ID: <1cff979e-1ec6-285d-f761-7acff17a3483@gmail.com>
Date: Sun, 22 Mar 2020 20:10:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <DM5PR13MB087674FC4FC989DE45C41E8ECBF30@DM5PR13MB0876.namprd13.prod.outlook.com>
Precedence: list
From: Marco Atzeri via Cygwin <cygwin@cygwin.com>
Reply-To: Marco Atzeri <marco.atzeri@gmail.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

Am 22.03.2020 um 18:50 schrieb Jay Libove via Cygwin:
> 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* (that matches the same .pdf files) DOES return the expected file list.
> 
> Example:
> 
> C:> DIR *.pdf
> Volume in drive C is C
> Volume Serial Number is 8674-712A
> 
> Directory of C:\Temp
> 
> 22/03/2020  18:30         1.675.954 test.pdf
> XX/XX/XXXX  XX:XX         {Any many other .pdf files}
> 
> Yet:
> 
> C:> ls *.pdf
> ls: cannot access '*.pdf': No such file or directory
> 
> And:
> C:> bash
> user@hostname /cygdrive/C/Temp/test
> $ ls *.pdf
> A.pdf
> B.pdf
> {etc}
> 
> And, not ALL of the *.pdf files in the particular directory where I've encountered this trigger the problem...
> 
> C:> ls N*.pdf
> N.pdf
> 
> C:> ls A*.pdf
> ls: cannot access 'A*.pdf': No such file or directory
> 
> Nor do all directories containing .pdf files produce this. Of the many thousands of files and directories that I have, only some produce this problem.
> In others, ls *.pdf works perfectly in Windows CMD.
> 
> I've looked at the Windows ATTRIB and CACLS of the files in directories where this problem occurs.
> They're all the same. That is, uniform across all files and directories. Nothing interesting.
> 
> It's not just 'ls':
> 
> C:> cat *.pdf
> cat: '*.pdf': No such file or directory
> 
> So, it appears to be Cygwin shell expansion, when executed under Windows CMD, which is provoking this strange behavior.
> Any ideas what could be causing this, and how to solve it?
> 
> many thanks,
> Jay
> 

any reason for NOT using a cygwin shell ?

for discrepancy check the ACLs of the files with "cacls"

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple