Re: Removing ^X in paths

2022-02-03 Thread Thomas Wolff
Am 03.02.2022 um 07:11 schrieb L A Walsh: On 2022/02/02 20:12, Dennis Heimbigner wrote: I am using 64bit. And it has nothing to do misreading characters. The ^X is described in this document: https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, Wow, I've never seen such a pa

Re: Removing ^X in paths

2022-02-03 Thread Corinna Vinschen
On Feb 2 21:12, Dennis Heimbigner wrote: > I am using 64bit. > And it has nothing to do misreading characters. > > The ^X is described in this document: > https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, > > There you will see this text: > > "If you don't want or can't use UTF-8 as

Re: Removing ^X in paths

2022-02-02 Thread L A Walsh
On 2022/02/02 20:12, Dennis Heimbigner wrote: I am using 64bit. And it has nothing to do misreading characters. The ^X is described in this document: https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, Wow, I've never seen such a pathname. What's an example of a filename tha

Re: Removing ^X in paths

2022-02-02 Thread Brian Inglis
On 2022-02-02 21:12, Dennis Heimbigner wrote: On 2/2/2022 7:23 PM, L A Walsh wrote: 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 con

Re: Removing ^X in paths

2022-02-02 Thread Thomas Wolff
Am 03.02.2022 um 05:12 schrieb Dennis Heimbigner: I am using 64bit. And it has nothing to do misreading characters. The ^X is described in this document: https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, There you will see this text: "If you don't want or can't use UTF-8 as cha

Re: Removing ^X in paths

2022-02-02 Thread Dennis Heimbigner
I am using 64bit. And it has nothing to do misreading characters. The ^X is described in this document: https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, There you will see this text: "If you don't want or can't use UTF-8 as character set for whatever reason, you will nevertheless

Re: Removing ^X in paths

2022-02-02 Thread L A Walsh
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

Removing ^X in paths

2022-02-02 Thread Dennis Heimbigner
It appears that windows now supports the UTF-8 codepage and generally allows UTF-8 everywhere that ASCII was supported. 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. -- Problem reports: https://cygwin.com/problems.h