From: Andrey Repin <anrdaemon@yandex.ru>
To: Jay Libove <libove@felines.org>, 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
Date: Sat, 28 Mar 2020 15:21:33 +0300 [thread overview]
Message-ID: <948246853.20200328152133@yandex.ru> (raw)
In-Reply-To: <DM5PR13MB087674FC4FC989DE45C41E8ECBF30@DM5PR13MB0876.namprd13.prod.outlook.com>
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. See below)
> ls *someotherwildcard* (that matches the same .pdf files) DOES return the expected file list.
Adding to the previous answers, in regard to "ls *.pdf" vs. "ls *.PDF" from
native shell, there's "glob:ignorecase" CYGWIN option that can amend your issue.
See https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
--
With best regards,
Andrey Repin
Saturday, March 28, 2020 15:19:24
Sorry for my terrible english...
prev parent reply other threads:[~2020-03-28 12:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 17:50 Jay Libove
2020-03-22 19:08 ` Paul Moore
2020-03-22 19:27 ` Jay Libove
2020-03-22 19:41 ` Paul Moore
2020-03-22 19:54 ` Jay Libove
2020-03-22 20:15 ` Paul Moore
2020-03-23 17:43 ` Andrey Repin
2020-03-23 18:34 ` Jay Libove
2020-03-23 19:13 ` Andrey Repin
2020-03-24 7:57 ` Thomas Wolff
2020-03-23 23:04 ` Marco Atzeri
2020-03-22 19:10 ` Marco Atzeri
2020-03-22 19:15 ` Paul Moore
2020-03-28 12:21 ` Andrey Repin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=948246853.20200328152133@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=libove@felines.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).