public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: configured FZF call fails since update from Cygwin 3.0.7 to 3.1.2
Date: Fri, 17 Jan 2020 19:30:00 -0000	[thread overview]
Message-ID: <CA+kUOam-DF_z13koTa4yg4k=hEfsby2tbdcpzZ2F1JQd3QvbwA@mail.gmail.com> (raw)
In-Reply-To: <AM0PR03MB6228AAC87663C0019B9ECED7BA310@AM0PR03MB6228.eurprd03.prod.outlook.com>

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

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

  reply	other threads:[~2020-01-17 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17  9:43 Trosi, Marco
2020-01-17 19:30 ` Adam Dinwoodie [this message]
     [not found]   ` <VI1PR03MB6239E12934D22AE0DBEEFF5DBA0C0@VI1PR03MB6239.eurprd03.prod.outlook.com>
2020-01-27 17:31     ` Adam Dinwoodie

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='CA+kUOam-DF_z13koTa4yg4k=hEfsby2tbdcpzZ2F1JQd3QvbwA@mail.gmail.com' \
    --to=adam@dinwoodie.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).