From: David Hansen <david.hansen@gmx.net>
To: emacs-devel@gnu.org
Subject: gdb-ui, dedicated windows
Date: Sat, 05 Jul 2008 09:58:26 +0200 [thread overview]
Message-ID: <87zlowwyn1.fsf@localhorst.mine.nu> (raw)
Hello,
when `gdb-many-windows' is nil some windows (e.g. the window displaying
the stack buffer) are dedicated.
This may make sense with `gdb-many-windows' set to t but I find it
pretty annoying with a nil value. I just looked at a long stack trace
displayed in the only window of the frame.
When I hit RET to jump to the interesting source Emacs popped up a new
frame. IMHO it's very bad behavior to pop up a frame unless explicitly
asked to do so.
Do these windows have to be dedicated?
Another smaller annoyance: IMHO the separate IO buffer shouldn't be in a
dedicated window even if `gdb-many-windows' is t. It just takes to much
space and makes it hard to look at two source files at the same time.
BTW, how about some key bindings to move around / display the gdb-ui
windows?
David
next reply other threads:[~2008-07-05 7:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 7:58 David Hansen [this message]
2008-07-05 10:02 ` gdb-ui, dedicated windows Nick Roberts
2008-07-05 10:52 ` David Hansen
2008-07-07 4:38 ` Nick Roberts
2008-07-08 7:06 ` Miles Bader
2008-07-08 7:18 ` Miles Bader
2008-07-08 23:39 ` Nick Roberts
2008-07-08 23:46 ` Miles Bader
2008-07-09 10:47 ` Nick Roberts
2008-07-15 13:37 ` Miles Bader
2008-07-15 21:50 ` Nick Roberts
2008-07-15 23:43 ` Miles Bader
2008-07-05 14:04 ` Miles Bader
2008-07-05 16:11 ` Tom Tromey
2008-07-07 5:20 ` Nick Roberts
2008-07-07 14:40 ` Tom Tromey
2008-07-07 16:14 ` tomas
2008-07-07 19:33 ` David Hansen
2008-07-07 19:47 ` Lennart Borgman (gmail)
2008-07-07 20:01 ` Tom Tromey
2008-07-07 20:09 ` Lennart Borgman (gmail)
2008-07-07 23:11 ` Stephen J. Turnbull
2008-07-07 23:03 ` Lennart Borgman (gmail)
2008-07-08 16:02 ` James Cloos
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=87zlowwyn1.fsf@localhorst.mine.nu \
--to=david.hansen@gmx.net \
--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 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.