[ANNOUNCEMENT] Updated: mutt-1.13.5-1

New version 1.3.5-1 of mutt is available in the Cygwin distribution: CHANGES Last upstream bugfix update release. Full details on: https://gitlab.com/muttmua/mutt/raw/master/UPDATING DESCRIPTION The Mutt E-Mail Client "All mail clients suck. This one just sucks less." Mutt is a small but v

Re: Sv: Sv: Sv: Sv: Named pipes and multiple writers

On 3/28/2020 11:43 AM, Ken Brown via Cygwin wrote: On 3/28/2020 8:10 AM, sten.kristian.ivars...@gmail.com wrote: On 3/27/2020 10:53 AM, sten.kristian.ivars...@gmail.com wrote: On 3/26/2020 7:19 PM, Ken Brown via Cygwin wrote: On 3/26/2020 6:39 PM, Ken Brown via Cygwin wrote: On 3/26/2020 6:01

Re: Request for additional ming-w64 binaries

> the following packages are missing static libraries, i.e *.a files Cygwin has always been bad about this, and I dont see that changing. And if you post an issue to the repo, it just gets closed: best bet would be to look at these

Re: WSL symbolic links

On 2020-03-28 05:59, Andrey Repin wrote: > Greetings, Brian Inglis! > >>> >>> Thanks! This should already be fixed in the latest developer snapshot >>> after I was finally able to install WSL myself. See my reply to Thomas >>> in https://sourceware.org/pipermail/cygwin/2020-March/244211.html >>>

Re: Sv: Sv: Sv: Sv: Named pipes and multiple writers

On 3/28/2020 8:10 AM, sten.kristian.ivars...@gmail.com wrote: On 3/27/2020 10:53 AM, sten.kristian.ivars...@gmail.com wrote: On 3/26/2020 7:19 PM, Ken Brown via Cygwin wrote: On 3/26/2020 6:39 PM, Ken Brown via Cygwin wrote: On 3/26/2020 6:01 PM, sten.kristian.ivars...@gmail.com wrote: The EN

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

Greetings, Jay Libove! > I've never seen this before. > In a Windows CMD shell, Cygwin shell expansion, for example: > ls *.pdf > returns: > ls: cannot access '*.PDF': No such file or directory > (Indeed, any Cygwin shell expansion, when executed from within Windows CMD, > produces this error. S

Sv: Sv: Sv: Sv: Named pipes and multiple writers

>On 3/27/2020 10:53 AM, sten.kristian.ivars...@gmail.com wrote: >>> On 3/26/2020 7:19 PM, Ken Brown via Cygwin wrote: On 3/26/2020 6:39 PM, Ken Brown via Cygwin wrote: > On 3/26/2020 6:01 PM, sten.kristian.ivars...@gmail.com wrote: >> The ENIXIO occurs when parallel child-processes sim

Re: WSL symbolic links

Greetings, Brian Inglis! >> >> Thanks! This should already be fixed in the latest developer snapshot >> after I was finally able to install WSL myself. See my reply to Thomas >> in https://sourceware.org/pipermail/cygwin/2020-March/244211.html >> >> All the effects are a result of not opening t

Re: WSL symbolic links

Am 28.03.2020 um 11:31 schrieb Henry S. Thompson via Cygwin: Brian Inglis writes: ... wished for a while: a program that would classify a file name as a (regular) hard link, a Windows directory or file link, a junction, a Windows shortcut, a Cygwin symlink, a Unix/WSL symlink, a URL link, and/

Re: WSL symbolic links

Brian Inglis writes: > ... wished for a while: a program that would classify a file name as > a (regular) hard link, a Windows directory or file link, a junction, a > Windows shortcut, a Cygwin symlink, a Unix/WSL symlink, a URL link, > and/or tell me where it links to etc. Thinking of hacking th