From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] unison2.48
Date: Fri, 05 Jun 2015 22:24:00 -0000 [thread overview]
Message-ID: <1433543067.14544.77.camel@cygwin.com> (raw)
In-Reply-To: <mj04naposnabjq8naf78f5qrce882q4aju@4ax.com>
On Fri, 2015-06-05 at 16:16 -0400, Andrew Schulman wrote:
> > On Fri, 2015-06-05 at 12:06 -0400, Andrew Schulman wrote:
> > BTW do you have any plans to build the GTK GUI versions?
>
> Not immediately. The last time I tried was several years ago, and there was
> some problem with lablgtk that kept it from working. That was many versions of
> unison and lablgtk ago, so it would be worth trying again, but only if people
> want it.
I have had a working lablgtk in Ports for some time now. Have you tried
that?
> For myself, I use command line unison every day, but have no need for the GUI.
> And there's a Windows native build GUI, which probably meets many users' needs,
> although not necessarily Cygwin users. So I don't know how many people would
> want the GTK GUI.
Well, I wouldn't outright replace the CUI version with the GUI (even
though IIRC the latter can work from the command-line as well with
DISPLAY unset) due to the additional dependencies, but as a separate
command it would be a plus.
--
Yaakov
next prev parent reply other threads:[~2015-06-05 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 16:06 Andrew Schulman
2015-06-05 18:46 ` Yaakov Selkowitz
2015-06-05 20:16 ` Andrew Schulman
2015-06-05 22:24 ` Yaakov Selkowitz [this message]
2015-06-06 1:59 ` Andrew Schulman
2015-06-11 12:16 ` Michael DePaulo
2015-06-11 12:51 ` Andrew Schulman
2015-06-12 1:24 ` Michael DePaulo
2015-06-12 7:54 ` lablgtk2 (was: [ITP] unison2.48) Andrew Schulman
2015-06-12 19:41 ` Yaakov Selkowitz
2015-06-12 20:40 ` Andrew Schulman
2015-06-12 21:31 ` Yaakov Selkowitz
2015-06-12 21:52 ` Andrew Schulman
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=1433543067.14544.77.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@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).