From: Syd Polk <spolk@redhat.com>
To: Chris Faylor <cgf@cygnus.com>,
"John A. Turner" <turner@blueskystudios.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight on Windows NT w/cygwin
Date: Mon, 12 Jun 2000 12:32:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20000612123258.00c27180@pop.cygnus.com> (raw)
In-Reply-To: <20000612153055.A6604@cygnus.com>
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 <cgf@cygnus.com>:
> >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.
next prev parent reply other threads:[~2000-06-12 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 11:55 MWCruess
2000-06-09 17:52 ` Chris Faylor
2000-06-12 11:04 ` John A. Turner
2000-06-12 12:31 ` Chris Faylor
2000-06-12 12:32 ` Syd Polk [this message]
2000-06-12 12:36 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2000-06-09 20:18 MWCruess
2000-06-08 19:58 MWCruess
2000-06-08 20:36 ` Chris Faylor
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=4.2.0.58.20000612123258.00c27180@pop.cygnus.com \
--to=spolk@redhat.com \
--cc=cgf@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=turner@blueskystudios.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).