Re: Removing ^X in paths

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

Getting trouble in installing the apps on kindle fire first generation

Hi, hope you will be in good health i have watched the video on you tube https://www.youtube.com/watch?v=2d4h3U4Mogg and tried to do the same on but failed to install all the steps that you have shared through Youtube video. so therefore It's my humble request kindly help me out to resolve this

Re: Log.text error

On 2022-02-02 21:34, Niclas Helbig wrote: The log Text told me to send you this. I am no Code-wizzard, so I dont really know what this means. I dont have Surface Wind Layer and WAFS Turbulence unfortunatly. Would really like to fix that but dont know how. ... 0 [main] WIN32wgrib2 5128 fi

Re: Removing ^X in paths

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

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

Log.text error

art of https://nomads.ncep.noaa.gov/pub/data/nccf/com/gfs/prod/gfs.20220202/18/atmos/gfs.t18z.pgrb2full.0p50.f009.idx with params: {'context': } Feb 03 05:18:51 Updating metar stations. Feb 03 05:18:51 Downloading part of https://aviationweather.gov/adds/dataserver_current/current/meta

Re: Removing ^X in paths

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: ls -C broken

On 2022/01/28 07:46, Thomas Wolff wrote: If I redirect output of `ls -C` (file / pipe), it used to produce well-formatted output in columns. Suddenly it produces garbage formatting instead. As `ls` itself is not new, maybe it's some library that breaks behaviour? Or even pty code?? Works on Cyg

Re: Removing ^X in paths

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

Re: Cntlm has crashed

>--_004_481dbdafcf4f490cb61aa737e27f04fbsexch1301corpssigovtnz_ >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: quoted-printable >Hi, >Cntlm has crashed with the below error: >1 [main] cntlm 20440 find_fast_cwd: WARNING: Couldn't compute FAST_CWD point= >er. Please repo

Cntlm has crashed

Hi, Cntlm has crashed with the below error: 1 [main] cntlm 20440 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com Attached the dump. Regards Tracen --- This

Removing ^X in paths

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

Re: Renaming (with 'mv') very large files is SLOW

On 2022/01/31 13:36, Adam Dinwoodie wrote: Could it be that the first 'mv' triggered an anti-virus read of the file since perhaps it detects it as a new/changed file? But if so, would 'mv' (under Task Manager) be showing the 100+ MB/s disk activity? That definitely seems plausible; the

makedepend does not honor UNC path for -I and -Y

cygwin makedepend collapses the double-slash UNC path prefix to one single slash. It fails to find headers via such search paths. Cygwin 3.2.0-1 on windows server 2012 R2 makedepend 1.0.6 -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Do