From: mray271 <mray271@gmail.com>
To: Russell VT <russellvt@gmail.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: Terminator 2.0
Date: Fri, 8 Oct 2021 22:40:20 -0700 [thread overview]
Message-ID: <3df03fb9-f77e-74bb-ab1d-f9bd941efa47@gmail.com> (raw)
In-Reply-To: <CANV2+nXoo1Fk65KcqOdiaOBrVoyvTKSJpCfkH641Q7SVxo7gTw@mail.gmail.com>
Hi Russel,
I create an issue here:
https://github.com/gnome-terminator/terminator/issues/523
On 10/8/21 4:25 AM, Russell VT wrote:
> This developer seems to have taken on the role as "main distributor,"
> rather than making this a simple Python module that's distributed
> through the likes of PyPy. Judging from the number of "unsupported"
> distributions/versions in their list,
> <https://github.com/gnome-terminator/terminator/blob/master/INSTALL.md>
> I would think you should take this up with the module owner, rather
> than with any Cygwin maintainer.
>
> If they would, instead, distribute this over a more-common
> software repository... then, maybe I would answer this differently.
>
> Cheers -
> RVT
>
>
> On Fri, Oct 8, 2021 at 12:59 AM mray271 via Cygwin <cygwin@cygwin.com>
> wrote:
>
>
> Now that Terminator development is reinvigorated and Python 3
> compat, is
> there a way I can get it working in Cygwin ?
>
> https://github.com/gnome-terminator/terminator
>
> Both the current offerings of Terminator and Guake are reliant on
> Python
> 2.7 and severely buggy or no longer working on Windows 10.
>
> Thanks!
>
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
>
>
> --
> Russell M. Van Tassell <russellvt@gmail.com>
prev parent reply other threads:[~2021-10-09 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 7:58 mray271
2021-10-08 11:25 ` Russell VT
2021-10-09 5:40 ` mray271 [this message]
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=3df03fb9-f77e-74bb-ab1d-f9bd941efa47@gmail.com \
--to=mray271@gmail.com \
--cc=cygwin@cygwin.com \
--cc=russellvt@gmail.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).