From: Nicholas Wourms <nwourms@netscape.net>
To: insight@sources.redhat.com
Subject: Re: Various problems and/or questions on Insight 5.2.1
Date: Tue, 03 Sep 2002 10:21:00 -0000 [thread overview]
Message-ID: <3D74EF68.5070405@netscape.net> (raw)
Hi,
Having discussed this with others on the Cygwin list, I'd
like to chime in on this thread. You said:
"Ugh. That means that more than just tcl and tk was messed
up by the "merge". [You know, I've often considered starting
over with the "port" to cygwin for 8.3 -- or with Mumit
Khan's work. It can't be nearly as botched as what we have
now.]"
If you do go this course, might I recomend that you use
Cygwin/XFree for the gui front end? The Cygwin/XFree
project is just a few months away from rootless mode. You
could have a tcl script automatically start the rootless x
in the background when the programmer starts up gdb. This
would make supporting Tk much easier because you'd no longer
have this limbo state between the Unix and Win32
implimentations of TclTk. The added benefit for some of us
is that it makes porting unix Tk based apps & libraries a
whole *hell* of a lot easier for the rest of us. You should
see in one of the following messages a patch to add such
functionality. Also of note is that the quest for Cygwin
mkfifo is back up and running, so hopefully we'll have that
soon. The serial communications function that used to be
missing in Cygwin is now complete.
As for your other question, this thread has somewhat
summerized what needs to be done to merge his port in these
messages [I'd reccomend reading the whole thread though]:
http://sources.redhat.com/ml/cygwin/2002-06/msg00422.html
http://sources.redhat.com/ml/cygwin/2002-06/msg00483.html
http://sources.redhat.com/ml/cygwin/2002-06/msg00552.html
I'm sure if you contacted Mumit, he'd be happy to assist in
merging the changes, as he pointed out in one of his posts.
Hopefully that will answer some of your earlier questions.
I really hope you'll considier this. I'd do it myself, but
I'm somewhat over-extended at the moment (I'm sure you are
too). Anyhow, feel free to disagree with my evaluation...
Cheers,
Nicholas
next reply other threads:[~2002-09-03 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 10:21 Nicholas Wourms [this message]
2002-09-04 8:42 ` Christopher Faylor
2002-09-04 8:45 ` Keith Seitz
2002-09-04 8:49 ` Christopher Faylor
2002-09-04 9:02 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 8:24 Nicholas Wourms
2002-09-05 9:39 ` Christopher Faylor
2002-09-05 10:08 ` Nicholas Wourms
2002-09-06 0:37 ` Kai Ruottu
2002-09-06 20:59 ` Christopher Faylor
2002-09-03 7:25 Ton van Overbeek
2002-08-30 4:11 LE GALLO Pierre OF/DSI/EXT
2002-08-30 10:38 ` Keith Seitz
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=3D74EF68.5070405@netscape.net \
--to=nwourms@netscape.net \
--cc=insight@sources.redhat.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).