X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.1 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_MJ,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4C781218.20004@cwilson.fastmail.fm>
References: <20100827182230 DOT 8007 DOT qmail AT web4111 DOT mail DOT ogk DOT yahoo DOT co DOT jp>	<AANLkTinVuCaQvBs-ENXDpF5Qk6Xu4dfdrrg3rhcOspwG AT mail DOT gmail DOT com>	<4C781218 DOT 20004 AT cwilson DOT fastmail DOT fm>
Date: Sat, 28 Aug 2010 16:31:50 +0200
Message-ID: <AANLkTinRHi3hKBViNo5bszm5=brVhLX_cpbv6eG=yT32@mail.gmail.com>
Subject: Re: gitk unusable in cygwin-1.7.6-1 because tcltk-20080420-1 is native win32 app.
From: Reini Urban <rurban AT x-ray DOT at>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2010/8/27 Charles Wilson:
> On 8/27/2010 2:33 PM, Andy Koppe wrote:
>> On 27 August 2010 19:22, neomjp wrote:
>>> 2. I understand that the reason to have tcltk-20080420-1 as a win32 app=
 is
>>> to have a graphical insight that does not depend on X Window.
>>
>> Cygwin programs can have Win32 interfaces actually, as proven by the
>> likes of rxvt, mintty, and the Xwin server itself.
>
> The real issue is that tcltk-20080420-1 presents the GDI (e.g. native
> windows) backend implementation for tcl/tk. =A0I was proposing that we
> eventually modify our offerings so that the new (probably split up)
> replacement package(s) present the X11 backend implementation instead.
>
> It has nothing to do with whether "tcltk" is a "win32" *application* as
> opposed to a cygwin one. =A0It's all about which interface the
> application/library uses to put graphics on the screen: GDI or X11.
>
> So far, nothing has occurred on that line AFAIK. =A0If it is to happen,
> the current maintainer has to just pull the trigger and say "we are
> going to do this". Existing maintainers of tcl/tk clients will then
> adapt; until (if) that happens, nothing will change.
>
> I think the big hangups were (a) insight (b) git (c) python-idle.
> insight might actually be dead or dying, not sure. =A0Obviously git and
> python-idle both work with X (on linux) so it's doable to convert --
> just a nuisance.

A big nuisance in my eyes.
Why do I have to start a xserver, when I can use native fast small GDI?

The PIPE problem appears elsewhere also, and will be fixed with 1.7.7.
--=20
Reini

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