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 08B53385800C
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis:	v=2.4 cv=cagXElPM c=1 sm=1 tr=0 ts=603d02e5
	a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17
	a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=te1EGT4yAAAA:8 a=8pif782wAAAA:8
	a=uYT-Tk0qkVT609LjNaIA:9 a=QEXdDO2ut3YA:10 a=zvuQ_vupYScA:10
	a=bG9rKQxxVKkA:10 a=sRI3_1zDfAgwuvI8zelB:22 a=RRElR4r2U1jGY2dU47NL:22
To:	cygwin AT cygwin DOT com
References:	<PA4PR03MB69437E82C15ECDD7203A8506FB9A9 AT PA4PR03MB6943 DOT eurprd03 DOT prod DOT outlook DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
Subject:	Re: bug in cygstart utility
Message-ID:	<b21f0310-29b0-c7b2-fa72-f00326fd93a7@SystematicSw.ab.ca>
Date:	Mon, 1 Mar 2021 08:06:11 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.8.0
MIME-Version:	1.0
In-Reply-To:	<PA4PR03MB69437E82C15ECDD7203A8506FB9A9@PA4PR03MB6943.eurprd03.prod.outlook.com>
X-CMAE-Envelope:	MS4xfMobIuMu6wUYdlBldRACDcrG7ETjFVhc5nBjNZAYnfS0HvPCRShjtLTyMxG0W4s2z5MyhlXU2292KJVSNHhSyK1LckVp40Oa/eBU4OqF+qNH1tCai957
	kTW0mGi882XngD3kHw1slEkmtj3s2+ow661TJVRQhf8PTcrKhrZ+jC9HT/W30yHhSjZCgHFKRhgMEd0auK80Y+rQSJAg4BzRsMQ=
X-Spam-Status:	No, score=0.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL,
	RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,
	SPF_NONE, 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
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 121F6IcE031039

On 2021-03-01 04:17, John Vincent via Cygwin wrote:
> I'm running cygwin on Windows 10, using UTF8 in English. I run cygwin bash 
> inside a cygwin mintty terminal. I've noticed a minor problem when using 
> cygstart with wildcard parameters.
> I type:
>	$ cygstart *.??p
> If there is a matching file then everything works as I expect. However if
> there is no matching file I get an error message as follows:
> Unable to start '.p': The specified file was not found.
> When I look at this using the "od" command I see the following:
> $ cygstart *.??p 2>&1 | od -tx1 -c
> 0000000  55  6e  61  62  6c  65  20  74  6f  20  73  74  61  72  74  20
>           U   n   a   b   l   e       t   o       s   t   a   r   t
> 0000020  27  ef  80  aa  2e  ef  80  bf  ef  80  bf  70  27  3a  20  54
>           ' 357 200 252   . 357 200 277 357 200 277   p   '   :       T
> 0000040  68  65  20  73  70  65  63  69  66  69  65  64  20  66  69  6c
>           h   e       s   p   e   c   i   f   i   e   d       f   i   l
> 0000060  65  20  77  61  73  20  6e  6f  74  20  66  6f  75  6e  64  2e
>           e       w   a   s       n   o   t       f   o   u   n   d   .
> 0000100  0a
>          \n
> It looks to me like cygstart is not outputting the correct UTF-8 for either
> the * character or the ? character. I think this is a bug.
To support POSIX path names, Cygwin allows any characters other than \0 and /, 
so it maps Windows special characters into the UTF-8 BMP PUA:

https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars

http://www.unicode.org/faq/private_use.html

https://en.wikipedia.org/wiki/Private_Use_Areas

It may also prefix unsupported codes in a code page with CAN/0x18.

The bug is in displaying in the error message the remapped string with 
undisplayable PUA characters, rather than either the reverse mapped string or 
the original input path name.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
--
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

- Raw text -