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.4.1 sourceware.org 9F23A3858C2C
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=tlinx.org
Authentication-Results:	sourceware.org; spf=pass smtp.mailfrom=tlinx.org
Message-ID:	<61FB3CA1.8000001@tlinx.org>
Date:	Wed, 02 Feb 2022 18:23:29 -0800
From:	L A Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	Dennis Heimbigner <dmh AT ucar DOT edu>
Subject:	Re: Removing ^X in paths
References:	<0255429a-409d-c17a-7b4d-8cbbfbea7255 AT ucar DOT edu>
In-Reply-To:	<0255429a-409d-c17a-7b4d-8cbbfbea7255@ucar.edu>
X-Spam-Status:	No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	SPF_HELO_NONE, SPF_PASS, TXREP,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) 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-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>
Cc:	cygwin AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 2132OE3O022504

On 2022/02/02 12:40, Dennis Heimbigner wrote:
> It appears that windows now supports the UTF-8 codepage.
>   
It has since early 2000's.
> I light of this, it seems time to change cygwin so it no longer adds those
> control-x (^X)  characters in e.g. path names.
>   
^x is ASCII.  Cygwin doesn't insert ^X characters in paths.

Perhaps you are thinking of '\' which looks like ï¿¥ (a capital 'Y' with 
2 horizontal lines, (Fullwidth Yen Sign  U+FFE5)...if that's the case, 
some 8-bit font
displayed that sign instead of a backslash in non-unicode locals.

Are you using a 32-bit or 64-bit version of Cygwin?  on what version of 
windows?

If you still use a 32-bit version, you might need to move to a 64-bit 
version.
I know the 32-bit version sometimes had the problem because it supported
fewer fonts and fewer characters at the same time.

You might check out your locale (if in english, try setting:
LC_CTYPE="en_US.UTF-8"
in your shell and also check that your used font has a backslash in the
0x7f position.

But in shell, ^x is usually a character to erase the whole line -- so it 
really
wouldn't do to have it in a PATH.

Hope this helps, and sorry if this is completely off base.

Linda

>
>   


-- 
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 -