From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Using gdb (windows popping up)
Date: Sun, 9 Jun 2019 12:09:08 -0400 [thread overview]
Message-ID: <20190609120908.019c5340@mistral> (raw)
In-Reply-To: <20190609115246.41281b50@mistral>
On Sun, 9 Jun 2019 11:52:46 -0400
jonetsu <jonetsu@teksavvy.com> wrote:
> ... until the debugging session starts. At which point emacs decides
> to create a new whole emacs app/window with the source code in it. It
> boldly replaces the source window with the debugged app's output
> window and throws the source into a new emacs instance.
Using sr-speedbar-open prior to starting gdb solves the problem of
popping up a new emacs instance. That is, sr-speedbar with the
following added in .emacs (which I found in stack exchange, regarding
speedbar not being able to use the current emacs frame)
(defadvice delete-other-windows (after
my-sr-speedbar-delete-other-window-advice activate) "Check whether we
are in speedbar, if it is, jump to next window." (let ()
(when (and (sr-speedbar-window-exist-p sr-speedbar-window)
(eq sr-speedbar-window (selected-window)))
(other-window 1)
)))
(ad-enable-advice 'delete-other-windows 'after
'my-sr-speedbar-delete-other-window-advice) (ad-activate
'delete-other-windows)
Since emacs/gdb will use speedbar anyways to display watch items, might
as well load it up front.
So this seems to resolve the problem with new instances popping up.
next prev parent reply other threads:[~2019-06-09 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 15:52 Using gdb (windows popping up) jonetsu
2019-06-09 16:09 ` jonetsu [this message]
2019-06-09 16:18 ` jonetsu
2019-06-09 16:58 ` jonetsu
2019-06-09 17:48 ` Óscar Fuentes
2019-06-09 18:31 ` Eli Zaretskii
2019-06-09 18:59 ` jonetsu
2019-06-09 19:13 ` Eli Zaretskii
2019-06-09 19:27 ` jonetsu
2019-06-09 19:33 ` Noam Postavsky
2019-06-09 19:48 ` jonetsu
2019-06-09 20:15 ` Noam Postavsky
2019-06-09 21:10 ` jonetsu
2019-06-09 22:36 ` Óscar Fuentes
2019-06-10 13:33 ` jonetsu
2019-06-10 13:44 ` Óscar Fuentes
2019-06-10 14:00 ` jonetsu
2019-06-10 15:44 ` Eli Zaretskii
2019-06-10 18:52 ` jonetsu
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=20190609120908.019c5340@mistral \
--to=jonetsu@teksavvy.com \
--cc=help-gnu-emacs@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.
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).