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. S
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 li
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:
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 und
that points towards a solution, but it certainly must be a
clue.
thanks,
Jay
-Original Message-
From: Andrey Repin
Sent: Monday 23 March 2020 18:44
To: Jay Libove ; cygwin@cygwin.com
Subject: Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such
file or
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 accente
;ls' does, so it makes sense that this works, and it supports the
> > theory that something weird is going on between how Cygwin does shell
> > expansion when under Windows CMD vs. when fully within the Cygwin
> > environment (under bash where of course bash is doing the sh
in@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
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 sugg
going on between how Cygwin does shell expansion when
> under Windows CMD vs. when fully within the Cygwin environment (under bash
> where of course bash is doing the shell expansion, and ls or other Cygwin
> commands don't have to).
>
> Does any of this help pinpoint the proble
problem further?
thanks again,
-Jay
-Original Message-
From: Paul Moore
Sent: 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
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
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,
prod
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
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
14 matches
Mail list logo
