From mboxrd@z Thu Jan 1 00:00:00 1970 From: Syd Polk To: Chris Faylor , "John A. Turner" Cc: insight@sourceware.cygnus.com Subject: Re: Insight on Windows NT w/cygwin Date: Mon, 12 Jun 2000 12:32:00 -0000 Message-id: <4.2.0.58.20000612123258.00c27180@pop.cygnus.com> References: <14661.9716.435831.289091@denmark.blueskystudios.com> <26.6c5bb43.26729762@cs.com> <20000609205234.A31688@cygnus.com> <20000612153055.A6604@cygnus.com> X-SW-Source: 2000-q2/msg00260.html At 03:30 PM 6/12/00 -0400, Chris Faylor wrote: >On Mon, Jun 12, 2000 at 02:03:32PM -0400, John A. Turner wrote: > >>>>>> "CF" == Chris Faylor : > >CF> Unfortunately, insight has always had only minimal ability to recognize > >CF> Cygwin paths. This is due to the fact that the tcl and tk DLLs are 98% > >CF> pure Windows and only the bare minimum support for cygwin paths > >CF> required to search for things like init.tcl, etc. > > > >could someone discuss the pros and cons of using a fully cygwin-aware > >version of tcl/tk? seems to me that's what most people using insight on > >cygwin would want anyway > > > >I just know that after using a native build of XEmacs for some time, I was > >much happier when I started using a cygwin build - seems it would be > >similar with insight > >Pro: insight would be able to use all UNIX-like features of Cygwin. > >Con: Somebody has to do it. Other con: People using Insight for native Windows development could get confused. Syd Polk spolk@redhat.com Engineering Manager +1 415 777 9810 x 241 Red Hat, Inc.