This is the mail archive of the
mailing list for the Cygwin project.
Re: configured FZF call fails since update from Cygwin 3.0.7 to 3.1.2
- From: Adam Dinwoodie <adam at dinwoodie dot org>
- To: cygwin at cygwin dot com, "Trosi, Marco" <marco dot trosi at continental-corporation dot com>
- Date: Mon, 27 Jan 2020 17:31:10 +0000
- Subject: Re: configured FZF call fails since update from Cygwin 3.0.7 to 3.1.2
- References: <CA+kUOam-DF_z13koTa4yg4k=hEfsby2tbdcpzZ2F1JQd3QvbwA@mail.gmail.com> <VI1PR03MB6239E12934D22AE0DBEEFF5DBA0C0@VI1PR03MB6239.eurprd03.prod.outlook.com>
On Wed, 22 Jan 2020 at 08:56, Trosi, Marco wrote:
> > Hi Marco,
> > On Fri, 17 Jan 2020 at 09:43, Trosi, Marco wrote:
> > >
> > > Hello everyone and a happy new year,
> > >
> > > I updated recently Cygwin from 3.0.7 to 3.1.2, and now when I run "fzf" the following happens.
> > >
> > > <snip>
> > While I'm nominally the Cygwin maintainer for fzf, the upstream
> > source has stopped supporting the version Cygwin uses, which means
> > there's incredibly little help I can offer.
> > I vaguely intended to create a supported fork of the Ruby fzf
> > version that Cygwin runs, but never managed to make any useful
> > progress on it. At this point, it's unlikely I'm ever going to,
> > either.
> > If you're interested in taking over the maintainership and working
> > out your problems yourself, that's something I'm definitely willing
> > to help with insofar as I can, but otherwise I'm afraid you're on
> > your own here.
> > (For context: the version of fzf that Cygwin uses is written in
> > Ruby, but some time ago the upstream fzf project switched from a
> > Ruby-based version to a Go-based version. Cygwin doesn't have a
> > native Go compiler, and getting a working Cygwin-packaged version of
> > fzf using a non-Cygwin Go compiler was beyond what I could achieve
> > with the time available to me.)
> > Adam
> Thanks for the offer.
> Do you really think it has something to do with FZF?
> FZF is working perfectly.
> The issue occurs only when I use my "fdc" wrapper script and since update to Cygwin 3.1.2.
> Currently it feels to me like some kind of Cygwin internal string/pipe/stream handling thing.
> Okay maybe Cygwin changed something on purpose and FZF needs to be updated accordingly, is that what you think is happening here?
I think it's unlikely that the problem is with FZF, however given that's
where you're spotting the problem, someone needs to narrow down what's
going on, and that'll require either digging into what FZF is doing, or
otherwise coming up with a simple test case that doesn't involve FZF.
As is more-or-less always the case with open source projects, someone
has to do that work. That might be me, as FZF maintainer, but as above,
I simply don't have the bandwidth to do that. It could be someone else
involved in the Cygwin project, but given nobody else has replied to
this thread on the Cygwin mailing list, I don't think you're likely to
have much luck waiting on that. Which, I'm afraid, leaves you.
If you can get a simple test case that shows the problem and doesn't
involve FZF, I expect other people on the list will be much better
placed to help. Until and unless that simple test case exists, however,
I think there's unlikely to be any more progress unless someone else
happens to discover the same problems by chance.
PS: Convention on this list, per the links in the email footer, is to
reply to the list, not to individuals, as it means everyone on the list
can help rather than requiring one person to do all the labour. We also
prefer to reply in-line below the text (as I'm doing here) and to not
quote raw email addresses, since otherwise they get harvested by
spammers from the email archives.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple