Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Greetings, Jay Libove! > 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.

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Am 23.03.2020 um 20:13 schrieb Andrey Repin: Greetings, Jay Libove! ... If I set LANG=en_US.UTF-8 in a Windows CMD window, **then the globbing problem goes away**. I was about to respond that cmd.exe does not do shell expansion but in fact there is a cygwin workaround to replace it with

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Am 23.03.2020 um 19:34 schrieb Jay Libove via Cygwin: Hi Andrey, (I have no idea what you mean about "top posting".) https://lmgtfy.com/?q=top+posting+vs+bottom+posting -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Greetings, Jay Libove! > Hi Andrey, > (I have no idea what you mean about "top posting".) https://cygwin.com/acronyms/#TOFU > `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

RE: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

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"

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Greetings, Jay Libove! Please no top posting in this mailing list. > Good suggestion, deleting files one by one. It's not just one file, but it > does seem to have something to do with some file name patterns. > I think I've got it. It's accented characters. > I live in Spain. Spanish has

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Interesting. Maybe codepage-related issues, then. Sorry, I'm out of my depth now, I'll leave it to someone else to diagnose further. On Sun, 22 Mar 2020 at 19:54, Jay Libove wrote: > > Good suggestion, deleting files one by one. It's not just one file, but it > does seem to have something to do

RE: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Good suggestion, deleting files one by one. It's not just one file, but it does seem to have something to do with some file name patterns. I think I've got it. It's accented characters. I live in Spain. Spanish has accented characters such as "Asociación". When I remove all files containing any

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Have you tried deleting files one by one, to see if the issue is related to a single file (sorry if this is an obvious suggestion that you've already tried). In Cygwin bash, it's the shell that glob-expands wildcards before calling your program (e.g. ls), and in find, it's the find code that does

RE: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Thanks Paul, both for your initial reply, and your follow-up. In this case it's not a matter case sensitivity. I've verified that, in one of the example cases, there are both *.pdf and *.PDF files in the subject directory. Both 'ls *.pdf' and 'ls *.PDF' produce the "ls: cannot access

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

On Sun, 22 Mar 2020 at 19:11, Marco Atzeri via Cygwin wrote: > any reason for NOT using a cygwin shell ? Many reasons. But that's not relevant to this thread, is it? (Note: I'm not the OP, just an interested contributor to the thread). I'm happy to elaborate if you want, but I suggest we do it

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

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,

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 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 this before. > In a Windows CMD shell, Cygwin

shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

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*