From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) by sourceware.org (Postfix) with ESMTPS id 25368388B034 for ; Mon, 18 May 2020 20:01:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 25368388B034 Received: by mail-oi1-x232.google.com with SMTP id y85so5388309oie.11 for ; Mon, 18 May 2020 13:01:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wSyaHu4BchYlEigEpKhw/ypvi1zGDfNNtnKv0chDQ+0=; b=VjR+EiNqngHkFhmi++36kDD+tZuBBVi28Gb9E/499jySprp14K24NH/Ij2inYNywcO NE+2gYlxnIRPa38OkEkWH15WbEsBMXgg1K9iKssMNgYHpspv1YewPnvMr2QMIXVwKfEF uUg8KAVsjcP7MkiJvPIzjIp4E1OC6rfWx3isbzQ31kux32tL0F0BMUtP9cvqd4B4hI+h EfrTTwPp0tA/J0QDfTBhwtvZ+PUbHSJpqjXVtBvG/dTFnItoFsBix5e0CEWEet9tFbqI bNNt7+VMjAo9/m7aeJJNpD5YiJkybVKc6PybIVZ9FDbC4lTAAUwXcdJ0vVZ8+KefeeKk s56g== X-Gm-Message-State: AOAM530zQb+qA1YXFL2Y3tk7LjStAN7DfEITUms3BzGrEV/i/jJHCmpy w5jY6PBznRNuxoGHuLxvygo3UqFUKCLJVcInfvo= X-Google-Smtp-Source: ABdhPJwmaQI/UCMcuF4Re5u+IA/nBg2vnrWzMU3K2cXbFyUIG7uhmE+LFhzKDYZukNhpfmM5qGAFhlqCicZefF3+UFQ= X-Received: by 2002:a05:6808:3af:: with SMTP id n15mr720085oie.43.1589832108241; Mon, 18 May 2020 13:01:48 -0700 (PDT) MIME-Version: 1.0 References: <4319b2cc-07c0-8739-f87d-2c2cebbecae7@jeffunit.com> <1975574327.20200518185545@yandex.ru> In-Reply-To: From: David Macek Date: Mon, 18 May 2020 22:01:36 +0200 Message-ID: Subject: Re: wildcards don't work in directory with files with odd characters To: Adam Dinwoodie Cc: cygwin Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, PDS_OTHER_BAD_TLD, 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@cygwin.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: , X-List-Received-Date: Mon, 18 May 2020 20:01:59 -0000 On Mon, May 18, 2020 at 8:07 PM Adam Dinwoodie 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. 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 could be at play, but I don't see why it would behave like this. -- David Macek