From: Enrico Forestieri <forenr@lyx.org>
To: cygwin@cygwin.com
Subject: Re: Issue with lyx and recent dll
Date: Wed, 3 Jun 2020 23:23:08 +0200 [thread overview]
Message-ID: <3c2eeb3b-19a3-7067-8bb9-924bb624b6ab@lyx.org> (raw)
In-Reply-To: <cf780c9a-9a5e-3e35-e5a3-d9efb5082736@cornell.edu>
On Wed, 03 Jun 2020 at 11:03:27PM +0200, Ken Brown wrote:
> There were some major changes in Cygwin's fifo implementation in
cygwin 3.1.0.
> It doesn't seem to have gotten a lot of testing until fairly recently,
when some
> bugs were discovered and fixed in cygwin 3.1.5. Have you tried the latter?
> (There's also some new functionality for fifos in cygwin 3.1.5, but I
doubt if
> that's relevant to your issue.)
Thanks Ken. Just installed cygwin 3.1.5 and the issue seems to have
gone. Great!
--
Enrico
next prev parent reply other threads:[~2020-06-03 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 10:50 Enrico Forestieri
2020-05-28 17:35 ` Marco Atzeri
2020-05-28 18:09 ` Marco Atzeri
2020-05-28 18:25 ` Enrico Forestieri
2020-05-28 20:01 ` Marco Atzeri
2020-05-29 15:29 ` Enrico Forestieri
2020-06-01 20:26 ` Marco Atzeri
2020-06-03 20:34 ` Enrico Forestieri
2020-06-03 21:02 ` Ken Brown
2020-06-03 21:23 ` Enrico Forestieri [this message]
2020-05-28 18:12 ` Enrico Forestieri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c2eeb3b-19a3-7067-8bb9-924bb624b6ab@lyx.org \
--to=forenr@lyx.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).