From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org, storm@cua.dk
Subject: Re: M-x gdb troubles
Date: Wed, 28 Apr 2004 17:44:29 +0100 [thread overview]
Message-ID: <16527.57197.463452.855021@nick.uklinux.net> (raw)
In-Reply-To: <jwv7jw6ivmd.fsf-monnier+emacs@gnu.org>
> > It could be split but, currently, the other debuggers couldn't use these
> > other windows.
>
> AFAIU, they indeed don't use most of them, but they all use "a source
> window", except that they just use pop-to-buffer to display it rather than
> gdb-source-window.
I don't quite follow as I removed gdb-source-window on 2004-04-08.
> I personally like the use of pop-to-buffer over gdb-source-window because of
> my Emacs setup so I'd like gdb-ui to be able to use this simpler gud
> scheme, but I expect other people will like the gdb-source-window kind of
> usage and will want it to be used for other gud modes as well.
gdb-ui now just uses gdb-display-buffer (a variant of gud-display-buffer from
gdba.el)
Also if you create new frames for the different buffers, say through the
menubar:
Gud->GDB-Frames->Threads
Breakpoints
Stack
...
then the bahaviour should be improved.
> Hence a sort of merge. As said, I'm proposing this without having really
> looked at the code, so it may be impractical. But I think we should move
> in this direction.
Are the changes that I have made in the direction that you are talking about?
Nick
next prev parent reply other threads:[~2004-04-28 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 19:16 M-x gdb troubles Nick Roberts
2004-04-21 20:30 ` Stefan Monnier
2004-04-21 22:57 ` Kim F. Storm
2004-04-21 22:09 ` Nick Roberts
2004-04-21 22:38 ` Miles Bader
2004-04-22 0:46 ` Kim F. Storm
2004-04-23 0:12 ` Nick Roberts
2004-04-23 15:07 ` Stefan Monnier
2004-04-28 16:44 ` Nick Roberts [this message]
2004-04-28 17:05 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2004-04-20 15:22 Kim F. Storm
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=16527.57197.463452.855021@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.