From: Chris Wagner <wagnerc@plebeian.com>
To: cygwin@cygwin.com
Subject: Re: wildcards don't work in directory with files with odd characters
Date: Mon, 18 May 2020 22:04:53 -0400 [thread overview]
Message-ID: <a7d47c2f06669dc94cf415e0460e9e42@plebeian.com> (raw)
In-Reply-To: <4319b2cc-07c0-8739-f87d-2c2cebbecae7@jeffunit.com>
On 2020-05-18 8:40 am, jeff wrote:
> I have a directory that has some files with odd files.
> I can do a 'ls', successfully. However if I do a 'ls *'' I get:
> ls: cannot access '*': No such file or directory
>
> Here is ls output:
> 'Highlander-S03E21-Final'$'\303\251''_Part_I-22.mkv'
> 'Highlander-S03E22-Final'$'\303\251''_Part_II-23.mkv'
I can confirm this. I've seen weirdo behavior before with Cygwin
commands having to interpret wild cards internally. It's probably
related to some wonky unicode optimization or incomplete wildcard
implementation. This falls under the category of "don't do that". :)
Mintty:
$ uname -a; cygcheck -c coreutils
CYGWIN_NT-6.1 applejack 3.1.0(0.340/5/3) 2019-11-19 13:58 x86_64 Cygwin
Cygwin Package Information
Package Version Status
coreutils 8.26-2 OK
wagnerc@applejack /tmp/wild
$ touch 'Highlander-S03E21-Final'$'\303\251''_Part_I-22.mkv'; dir *
-rw-rw-r--+ 1 0 May 18 21:46 foo
-rw-rw-r--+ 1 0 May 18 21:55 Highlander-S03E21-Finalé_Part_I-22.mkv
CMD:
C:\cygwin64\tmp\wild>dir
Volume in drive C is INTELWINNT
Volume Serial Number is 642B-E7BA
Directory of C:\cygwin64\tmp\wild
05/18/2020 09:46 PM <DIR> .
05/18/2020 09:46 PM <DIR> ..
05/18/2020 09:46 PM 0 foo
05/18/2020 09:55 PM 0
Highlander-S03E21-Finalé_Part_I-22.mkv
2 File(s) 0 bytes
2 Dir(s) 35,887,038,464 bytes free
C:\cygwin64\tmp\wild>ls
'Highlander-S03E21-Final'$'\303\251''_Part_I-22.mkv' foo
C:\cygwin64\tmp\wild>ls *
ls: cannot access '*': No such file or directory
C:\cygwin64\tmp\wild>ls f*
foo
C:\cygwin64\tmp\wild>ls H*
ls: cannot access 'H*': No such file or directory
Thanks.
prev parent reply other threads:[~2020-05-19 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 12:40 jeff
2020-05-18 15:55 ` Andrey Repin
2020-05-18 16:21 ` jeff
2020-05-18 18:03 ` Adam Dinwoodie
2020-05-18 18:10 ` jeff
2020-05-18 20:01 ` David Macek
2020-05-18 20:12 ` jeff
2020-05-19 10:49 ` Andrey Repin
2020-05-19 19:08 ` Chris Wagner
2020-05-19 2:04 ` Chris Wagner [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=a7d47c2f06669dc94cf415e0460e9e42@plebeian.com \
--to=wagnerc@plebeian.com \
--cc=cygwin@cygwin.com \
/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).