From: Thomas Wolff <towo@towo.net>
To: 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: Tue, 24 Mar 2020 08:57:12 +0100 [thread overview]
Message-ID: <d94c54dc-da38-f1a5-3599-c86f60c618a3@towo.net> (raw)
In-Reply-To: <861475261.20200323221300@yandex.ru>
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 library-run
expansion. Maybe it's done before the locale is set up in cygwin dll?
Could the order be reversed?
Thomas
>> I'm not sure how that points towards a solution, but it certainly must be a clue.
> I have LANG=ru_RU.UTF-8 set in the user environment, but i have an autostart
> script for cmd.exe to set LANG=ru_RU.CP866 when I want to work in plain
> command prompt. But then again, I have code in ~/.bashrc which would
>
> 1. chcp 65001
> 2. export "LANG=$(locale -uU)"
>
> which helps transitioning from native applications to (saner) Cygwin environment.
>
>
next prev parent reply other threads:[~2020-03-24 7:57 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 [this message]
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
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=d94c54dc-da38-f1a5-3599-c86f60c618a3@towo.net \
--to=towo@towo.net \
--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).