From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 11365@debbugs.gnu.org, sds@gnu.org
Subject: bug#11365: 24.1.50; quitting gdb does not restore window configuration
Date: Tue, 01 May 2012 18:54:52 +0300 [thread overview]
Message-ID: <83zk9rsxpv.fsf@gnu.org> (raw)
In-Reply-To: <4F9F9A1D.3010605@gmx.at>
> Date: Tue, 01 May 2012 10:09:01 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 11365@debbugs.gnu.org
>
> >> Which command does "quit" run - `gdb-delete-frame-or-window'?
> >
> > dunno. the code indicates that, but the function seems too simple to
> > remove all those subordinate windows and buffers.
>
> So you have to check your key bindings ;-)
No, he doesn't. The function to look at is gdb-reset.
(gdb-delete-frame-or-window is just what causes GDB to quit, but when
it actually does, the comint process sentinel kicks in and calls
gdb-reset.) But for gdb-reset to do what Sam wants, gdb-setup-windows
should record the configuration of windows before it sets up the GDB
windows, otherwise we will have no information about the previous
window configuration.
next prev parent reply other threads:[~2012-05-01 15:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 18:40 bug#11365: 24.1.50; quitting gdb does not restore window configuration Sam Steingold
2012-04-27 19:01 ` Eli Zaretskii
2012-04-27 19:34 ` Sam Steingold
2012-04-28 6:51 ` Eli Zaretskii
2012-04-28 8:25 ` martin rudalics
2012-04-30 22:14 ` Sam Steingold
2012-05-01 8:09 ` martin rudalics
2012-05-01 12:25 ` Sam Steingold
2012-05-02 9:39 ` martin rudalics
2012-05-02 14:16 ` Sam Steingold
2012-05-05 9:42 ` martin rudalics
2012-05-06 5:40 ` Sam Steingold
2012-05-06 10:25 ` martin rudalics
2020-09-27 12:41 ` Lars Ingebrigtsen
2020-09-27 12:56 ` Eli Zaretskii
2020-09-27 13:00 ` Lars Ingebrigtsen
2020-09-27 13:02 ` Eli Zaretskii
2022-04-25 15:05 ` Lars Ingebrigtsen
2022-05-24 12:51 ` Lars Ingebrigtsen
2012-05-01 15:54 ` Eli Zaretskii [this message]
2012-05-02 9:40 ` martin rudalics
2012-05-02 16:02 ` Eli Zaretskii
2012-05-05 9:42 ` martin rudalics
2012-05-05 9:49 ` Eli Zaretskii
2012-05-05 10:24 ` martin rudalics
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=83zk9rsxpv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11365@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=sds@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).