From: David Macek <david.macek.0@gmail.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: wildcards don't work in directory with files with odd characters
Date: Mon, 18 May 2020 22:01:36 +0200 [thread overview]
Message-ID: <CAH2Hv8JdVWzh9KPaeoiC5_voEpS3KqyqUWB_GU4vrjQOEEWCMw@mail.gmail.com> (raw)
In-Reply-To: <CA+kUOakpSETMesmnnnazr+50r37tCJ0Ua=+LOXsEdtaEC0=cTQ@mail.gmail.com>
On Mon, May 18, 2020 at 8:07 PM Adam Dinwoodie <adam@dinwoodie.org> wrote:
> Cygwin's `ls` expects the
> shell (e.g. Bash) to expand globs like `*`, but Windows' command
> prompt expects applications to handle expanding globs (or the Windows
> equivalents thereof) themselves. When you call a Cygwin command like
> `ls` directly from the Windows command prompt, Windows passes the
> arguments as-is to the Cygwin command, and the Cygwin command assumes
> that the arguments it received are already appropriately expanded.
This is actually false. The official FAQ mentions it as well
here<https://cygwin.com/faq.html#faq.api.globbing>.
I went on to investigate what's the issue, but I can't replicate it.
Things like the console code page, the system code
page<https://www.digitalcitizen.life/changing-display-language-used-non-unicode-programs>
could be at play, but I don't see why it would behave like this.
--
David Macek
next prev parent reply other threads:[~2020-05-18 20:01 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 [this message]
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
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=CAH2Hv8JdVWzh9KPaeoiC5_voEpS3KqyqUWB_GU4vrjQOEEWCMw@mail.gmail.com \
--to=david.macek.0@gmail.com \
--cc=adam@dinwoodie.org \
--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).