X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:mime-version:subject:message-id:from:date :content-type:content-transfer-encoding; q=dns; s=default; b=Fll m17/pu04P7oK0qFR/x7Vs0CyzKcOLO16Uf8GzuEGHDMcnQHhKAkdCIssBFeK3puN jitHyq4G8faZD8+TOOlw0e2gWEFBwlEGYUnhEwvR8anm8oB0ezeo+kOI0tKpElWV CUPcYtiCYvd+AOIh2aVL64NqyTBGrx3wrzoNa9cs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:mime-version:subject:message-id:from:date :content-type:content-transfer-encoding; s=default; bh=I3mlR0cCe 4zi5I0AUIEDJZDT+Tc=; b=WvR+C6pBGAlyjapL078dY6S6DTf4aIj8tipGH0cUR 5dW6CnHCAbG5rRcONZwkm+2P1mzMo/2JtyOZ0Ge8IeM9ESGhshVIm3VAq+vdEoDa 71jwPjAK2ST1X3A2d7yR+xetbAfIaSfVv1rODL9DTkVZl6ltOQNY5VlPHb7ctMy8 cM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_50,BODY_8BITS,GARBLED_BODY,GIT_PATCH_2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 spammy=H*F:D*co.jp, 2100, japanese, Japanese X-HELO: inmx23.olympus.co.jp To: cygwin AT cygwin DOT com MIME-Version: 1.0 Subject: cmd.exe and file name conversion from comman line argument X-KeepSent: ADDE98D4:BA910041-492582D7:00014612; type=4; name=$KeepSent Message-ID: From: h_ono AT ot DOT olympus DOT co DOT jp Date: Fri, 27 Jul 2018 09:56:54 +0900 Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w6R0vD38004031 Hello, There is strange behavior when naming a file from command line argument in cmd.exe cosole, using touch or mv. I use: touch (GNU coreutils) 8.26 Packaged by Cygwin (8.26-2) cygwin1.dll version 2.10.0 in cmd.exe, doing > touch aaa and > touch 'aaa' give same file name aaa. > ls aaa but, when I use Japanese characters as file name, it gives different file names with and without the quote. > env LANG=ja_JP.UTF-8 touch あああ gives > env LANG=ja_JP.UTF-8 ls あああ but, > env LANG=ja_JP.UTF-8 touch 'あああ' gives file name with quote not stripped. > env LANG=ja_JP.UTF-8 ls 'あああ' If called from mintty + bash, $ env LANG=ja_JP.UTF-8 touch 'あああ' gives $ env LANG=ja_JP.UTF-8 ls あああ The problem is when I create a file containing spaces in its name. Creating a file in cmd.exe like: > env LANG=ja_JP.UTF-8 touch 'ああ あ' gives > env LANG=ja_JP.UTF-8 ls "'ああ あ'" (which is a file named 'ああ あ', not ああ あ) It seems, there is no way to create a file containing a space in its name, like ああ あ with commands such as touch or mv. Is it a normal behavior, or a bug? Is there any way to create a file containing Japanese characters and spaces in its name without quote added? FYI, With old cygwin (cygwin1.dll version 1.5.25), there were not such problem. Even from cmd.exe, > touch 'ああ あ' gave a file named 'ああ あ' (without the quote in real.) ---------- Hiroo Ono -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple