[Nitpicks] Non-standard Cygwin-only hashbangs in base-files, biber, hg, xlsx2csv, xmlto scripts

Hi folks, Running file(1) detects non-standard Cygwin-only hashbangs in base-files, biber, hg, xlsx2csv, xmlto scripts. If standard paths were used, these would be detected and named in file(1) output as POSIX shell, Perl, Python, etc. scripts. The use of /usr/bin/sh instead of standard /bin/sh,

Re: chere: Add cygwin icon to context menu

On Wed, Jul 26, 2017 at 1:33 PM, Doug Henderson wrote: > On 26 July 2017 at 11:08, Brian Mathis wrote: >> For anyone using 'chere' interested in having the Cygwin icon in the >> context menu, you can use the following commands: >> > > On Win7, chere has installed icons for me

Re: Unicode width data inconsistent/outdated

Am 26.07.2017 um 11:50 schrieb Corinna Vinschen: On Jul 26 03:16, Yaakov Selkowitz wrote: On 2017-07-26 03:08, Corinna Vinschen wrote: On Jul 26 08:49, Thomas Wolff wrote: It would be good to keep wcwidth/wcswidth in sync with the installed Unicode data version (package unicode-ucd).

Re: how to access and display apps that I've launched

On Wed, 7/26/17, Brian Inglis <> wrote: Subject: Re: how to access and display apps that I've launched To: cygwin Date: Wednesday, July 26, 2017, 1:07 PM > Anyway, Achim can easily fix this. You can fix this locally quickly using: $ fgrep

Re: how to access and display apps that I've launched

On Wed, 7/26/17, Achim Gratz <> wrote: Subject: Re: how to access and display apps that I've launched To: cygwin Date: Wednesday, July 26, 2017, 1:13 PM Ian Lambert via cygwin writes: > Indeed, Cygwin is installed on a FAT32 formatted >

Re: chere: Add cygwin icon to context menu

On 26 July 2017 at 11:08, Brian Mathis wrote: > For anyone using 'chere' interested in having the Cygwin icon in the > context menu, you can use the following commands: > On Win7, chere has installed icons for me since 23 Jan 2014 on 64 bit and 12 Aug 2016 for 32 bit. Note that the path to the

Re: how to access and display apps that I've launched

Ian Lambert via cygwin writes: > Indeed, Cygwin is installed on a FAT32 formatted > external drive, which is limited to 1980-01-01 on > the early end. Yes, that's the problem. Oh well, a braindead fs, where have I seen that before… is there any other such system in use that somebody would want

chere: Add cygwin icon to context menu

For anyone using 'chere' interested in having the Cygwin icon in the context menu, you can use the following commands: regtool -w -s set /HKCU/Software/Classes/Drive/Shell/cygwin64_bash/Icon 'C:\cygwin64\Cygwin-Terminal.ico' regtool -w -s set

Re: how to access and display apps that I've launched

On 2017-07-26 08:59, Ken Brown wrote: > On 7/26/2017 10:19 AM, Ian Lambert via cygwin wrote: >> Indeed, Cygwin is installed on a FAT32 formatted >> external drive, which is limited to 1980-01-01 on >> the early end. >> >> So apparently rebase has not been working for me >> "forever," > > More

Re: Sparse files in Cygwin

On 07/26/2017 12:02 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: > Hello, > > I have a question whether sparse files are supported in Cygwin. From the > source code, > it looks like they are, but from the series of the following commands, I > can't confirm: They are, but only if you

Sparse files in Cygwin

Hello, I have a question whether sparse files are supported in Cygwin. From the source code, it looks like they are, but from the series of the following commands, I can't confirm: $ dd bs=1 seek=1G if=/dev/null of=sparse 0+0 records in 0+0 records out 0 bytes copied, 0.00392699 s, 0.0 kB/s

Re: how to access and display apps that I've launched

On 7/26/2017 10:19 AM, Ian Lambert via cygwin wrote: Indeed, Cygwin is installed on a FAT32 formatted external drive, which is limited to 1980-01-01 on the early end. So apparently rebase has not been working for me "forever," More generally, it seems that the autorebase postinstall script

Re: how to access and display apps that I've launched

On Tue, 7/25/17, Brian Inglis <> wrote: Subject: Re: how to access and display apps that I've launched To: cygwin@cygwin.com Date: Tuesday, July 25, 2017, 8:09 PM Unless you are on some FAT or other legacy filesystem that might object to

Re: Updated: pinentry-1.0.0-2

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

Re: Unicode width data inconsistent/outdated

On Jul 26 03:16, Yaakov Selkowitz wrote: > On 2017-07-26 03:08, Corinna Vinschen wrote: > > On Jul 26 08:49, Thomas Wolff wrote: > >> It would be good to keep wcwidth/wcswidth in sync with the installed > >> Unicode data version (package unicode-ucd). > >> Currently it seems to be hard-coded (in

Re: Unicode width data inconsistent/outdated

On 2017-07-26 03:08, Corinna Vinschen wrote: > On Jul 26 08:49, Thomas Wolff wrote: >> It would be good to keep wcwidth/wcswidth in sync with the installed >> Unicode data version (package unicode-ucd). >> Currently it seems to be hard-coded (in newlib/libc/string/wcwidth.c); >> it refers to

Re: Unicode width data inconsistent/outdated

On Jul 26 08:49, Thomas Wolff wrote: > It would be good to keep wcwidth/wcswidth in sync with the installed > Unicode data version (package unicode-ucd). > Currently it seems to be hard-coded (in newlib/libc/string/wcwidth.c); > it refers to Unicode 5.0 while installed Unicode data suggest 9.0

Unicode width data inconsistent/outdated

It would be good to keep wcwidth/wcswidth in sync with the installed Unicode data version (package unicode-ucd). Currently it seems to be hard-coded (in newlib/libc/string/wcwidth.c); it refers to Unicode 5.0 while installed Unicode data suggest 9.0 would be used. I can provide some scripts to