X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org F0FF3385B831 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=yandex.ru Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=anrdaemon AT yandex DOT ru DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1584991201; bh=bVEy2CTRhhVtkzy2igNSrJZLEaCEYEunGqAURlmvgCM=; h=In-Reply-To:Subject:To:Reply-To:From:Message-ID:References:Date; b=TlnPsPyY1fiNPTvqUBggH2zCzXOmFZLQRnt/W5s+GhdW9uQVGjPzeRoilx+qvSBEJ XX906Df9RjNHVugRtXR0piII8wL7U9loD9etxBaT9ZaqS2ALOQmsQH1KKZVbkPCAbW hNulDYdbpkmPuMfCJeeeRvMgK8CCt9SV7WmmMLg8= Authentication-Results: mxback23g.mail.yandex.net; dkim=pass header.i=@yandex.ru Date: Mon, 23 Mar 2020 22:13:00 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home X-Priority: 3 (Normal) Message-ID: <861475261.20200323221300@yandex.ru> To: Jay Libove , cygwin AT cygwin DOT 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 In-Reply-To: References: <1141191582 DOT 20200323204357 AT yandex DOT ru> MIME-Version: 1.0 X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" 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 under Windows CMD: > LANG= > LC_CTYPE="C.UTF-8" > LC_NUMERIC="C.UTF-8" > LC_TIME="C.UTF-8" > LC_COLLATE="C.UTF-8" > LC_MONETARY="C.UTF-8" > LC_MESSAGES="C.UTF-8" > LC_ALL= > Aha, wait! No, there is one difference: in Cygwin Terminal (which I've > never run before today; I've always either just run commands in a CMD > window, or run bash.exe first; I'd initially mistakenly assumed that Cygwin > terminal was the same as bash-in-CMD, but clearly it's not): > LANG=en_US.UTF-8 > If I set LANG=en_US.UTF-8 in a Windows CMD window, **then the globbing problem goes away**. > 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. -- With best regards, Andrey Repin Monday, March 23, 2020 22:02:08 Sorry for my terrible english... -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple