public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Jim Ingham <jingham@apple.com>
Cc: Ken Moore <KMoore@gse-inc.com>, insight@sourceware.cygnus.com
Subject: Re: Hi,
Date: Wed, 21 Jun 2000 13:48:00 -0000	[thread overview]
Message-ID: <20000621164821.A25186@cygnus.com> (raw)
In-Reply-To: <B5767311.1883%jingham@apple.com>

On Wed, Jun 21, 2000 at 01:26:41PM -0700, Jim Ingham wrote:
>Yeah, I don't like this at all.  I always thought that the flashing console
>thingie was truely lame,. and made Insight look really bad. IIRC, the only
>reason that we didn't build with -subsystem-windows (sic), and thus
>eliminate this particular wart was that in the bad ole days the only way to
>run the gdb testsuite on Windows was to telnet in and use expect, and that
>required -subsystem-console.  Now that you can run the testsuite on Windows
>successfully, there is no good reason for this.

I believe that if you use -subsystem=windows then 'gdb -nw' wouldn't
work.  Wasn't that the case?  I guess I should just check this.

I hate that flashing console window, too.  I spent some time trying to
get get rid of it a copule of years ago but it seemed like Microsoft had
gone out of their way to make it difficult to do anything at all
sophisticated with console windows.  The flashing console window was the
best available compromise.

>> We were discussing trapping startup errors and displaying them in
>> a pop-up window but I don't think there is any simple mechanism for
>> doing that.
>
>Yeah, I was hoping that you could do something really simple like register a
>readable file-event for stderr, and respond to output there, but it looks
>like Tcl doesn't open stderr readable, and I have no idea what havoc doing
>this would wreak...  OTOH, things like the TkCon extension are able to
>redirect all the standard channels into a text widget, all from Tcl.  It
>might be a good idea to have a look at what TkCon does, and just copy that
>early on in the startup process...

I think that Keith suggested something similar.  I've Cc'ed him.

cgf

  reply	other threads:[~2000-06-21 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-21  6:58 Hi, Ken Moore
2000-06-21  7:06 ` Hi, Fernando Nasser
2000-06-21 11:29 ` Hi, Jim Ingham
2000-06-21 12:52   ` Hi, Chris Faylor
2000-06-21 13:26     ` Hi, Jim Ingham
2000-06-21 13:48       ` Chris Faylor [this message]
2000-06-21  8:07 Hi, Ken Moore
2000-06-21  8:33 ` Hi, Fernando Nasser
2000-06-21  8:40 ` Hi, Chris Faylor
2000-06-21 13:43 Hi, Ken Moore

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=20000621164821.A25186@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=KMoore@gse-inc.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=jingham@apple.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).