public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: James Ingham <jingham@cygnus.com>
To: Michael Abd-El-Malek <mabdelma@uwaterloo.ca>
Cc: insight@sourceware.cygnus.com
Subject: Re: You guys rock!
Date: Mon, 13 Mar 2000 10:31:00 -0000	[thread overview]
Message-ID: <14541.13462.744081.649302@leda.cygnus.com> (raw)
In-Reply-To: <38CAEEEB.63272003@uwaterloo.ca>

Michael,

This is not quite the solution I want to implement.  Turns out the
console window is not an XTerm, but a Tk Text window.  This has some
nice features, and I want to keep it around so I can do things like
switch it from a gdb command-line window to a direct conduit to the
Tcl interpreter living in Insight.  

However, this means that it would be hard to use this console for
terminal I/O, since I don't really want to write a real terminal I/O
package for Tk text widgets (including raw mode...)

The real solution is to have a "Program Output" window, separate from
the gdb command window.  There are a few times where it is nice to
have commands & output interleaved, but most of the time this is just
a pain.  Having a separate window is better in the long run, I think.

Now I just have to find time to implement this.  It is a bit of a
bear, since you have to get into gdb at the point where it launches
the inferior, and connect the std channels for the child to an XTerm
you have cooked up...  But doable.

Jim

 > Ok I found the "answer" to that question!
 > I had another annoying thing to report: the output of the program doesn't
 > go to the Console window, but rather to the terminal that started gdb.
 >  What do you guys think about that?  To me, it seems to be more convenient
 > for the output to go to the Console window, like DDD does...
 > Thanks!
 > Michael
 > 
 > Michael Abd-El-Malek wrote:
 > 
 > > I tried Insight for the first time now... I've been looking at it for a
 > > while, and finally I got the time to install it!
 > > It's great! All the windows are really useful... The only drawback is
 > > the use of Tcl/Tk, which makes the windows load slowers... But this is a
 > > minor irritance...
 > > One question though: in the register window, how do I make the fields
 > > narrower? They're really wide right now and they take up plenty of
 > > screen real-estate... Is it possible to resize them?
 > > All in all, this frontend is really nice and good job!
 > > Keep up the good work,
 > > Michael Abd-El-Malek
 > > 2nd year computer engineering student, University of Waterloo
 > 
 > 

-- 
++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++==++
Jim Ingham                                              jingham@cygnus.com
Cygnus Solutions, a Red Hat Company                      

      reply	other threads:[~2000-03-13 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-11 11:14 Michael Abd-El-Malek
2000-03-11 17:10 ` Michael Abd-El-Malek
2000-03-13 10:31   ` James Ingham [this message]

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=14541.13462.744081.649302@leda.cygnus.com \
    --to=jingham@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=mabdelma@uwaterloo.ca \
    /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).