unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gdba probs
Date: Sat, 7 Dec 2002 21:27:57 -0500	[thread overview]
Message-ID: <20021208022757.GA8446@gnu.org> (raw)
In-Reply-To: <E18KmST-0005cp-00@fencepost.gnu.org>

On Sat, Dec 07, 2002 at 04:25:57PM -0500, Richard Stallman wrote:
>     The totalview debugger starts with 6 windows. But, hey!, lets be open
>     minded about this. How do you know you don't want them before you know
>     what they do ?
> 
> Is there a way to make it more self-evident what these windows do?
> What measures are taken in the code as it is now
> to show the user what these windows do and how to use them?

The meaning of the windows should be pretty obvious to most people who have
some debugger experience I think; at least they were to me.  I presumed when
Nick said that, he meant it as a joke.

THe bigger problem is that they simply aren't very useful unless they have
some contents; until then they're just a waste of space -- and in many cases
they're a wast of space even if they _do_ have some contents, because the
contents are not something you want to see continuously (for instance the
breakpoints window).  The set of windows you want is highly dependent on what
you're debugging.

The GUI debuggers I've used typically start out displaying only one or two
windows (e.g., the command window and a source window, sort of like normal
gud mode), but offer toolbar buttons to easily pop up others; once the others
are popped up, they are updated continuously.  Note that for some window
types, you can pop up more than one instance -- e.g. memory display windows,
where you may want to display several regions of memory simultaneously.

Since screen-space is a fairly precious commodity for me this is a very good
method of operation (and I suspect the same is true of many users -- not
everyone uses a 1600x1280 display with an 8 point font!).

I gather that gdba is modelled after GUI debuggers that initially pop up many
very small windows; I've seen these, but don't like them, largely for the
reasons stated above (the other reason is that such debuggers usually seem to
use an `every window has a different obnoxious neon background color' look; I
guess they do this so you can sort out all those windows easily, but man it's
ugly!).

-Miles
-- 
Is it true that nothing can be known?  If so how do we know this?  -Woody Allen

  parent reply	other threads:[~2002-12-08  2:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 20:40 gdba probs Nick Roberts
2002-12-05 21:49 ` Stefan Monnier
2002-12-07  2:38   ` Nick Roberts
2002-12-07  3:10     ` Miles Bader
2002-12-09 15:46     ` Stefan Monnier
2002-12-10 14:19     ` Stefan Monnier
     [not found]       ` <15862.30022.647969.267154@nick.uklinux.net>
     [not found]         ` <200212111411.gBBEBUn03805@rum.cs.yale.edu>
2002-12-11 22:27           ` Nick Roberts
2002-12-11 22:48             ` Stefan Monnier
2002-12-12  0:05               ` Nick Roberts
2002-12-12 13:49                 ` Stefan Monnier
2002-12-12 14:13                   ` Miles Bader
2002-12-13 22:21                 ` Richard Stallman
2002-12-12  1:24             ` Miles Bader
2002-12-12 10:22               ` Kim F. Storm
2002-12-15  0:36   ` Nick Roberts
2002-12-07 21:25 ` Richard Stallman
2002-12-08  1:55   ` Nick Roberts
2002-12-09 20:21     ` Richard Stallman
2002-12-10 21:39       ` Nick Roberts
2002-12-10 23:44         ` Kim F. Storm
2002-12-11 20:40         ` Richard Stallman
2002-12-08  2:27   ` Miles Bader [this message]
2002-12-10 14:14     ` Stefan Monnier
2002-12-11 17:45       ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-12-05  6:19 Miles Bader

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021208022757.GA8446@gnu.org \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).