From: jonetsu <jonetsu@teksavvy.com>
To: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Using gdb (windows popping up)
Date: Sun, 9 Jun 2019 17:10:36 -0400 [thread overview]
Message-ID: <20190609171036.18a89cb0@mistral> (raw)
In-Reply-To: <CAM-tV-9mRYZz-xg8vUjrY39Z8VpU5n+p-kBTj2zvaW5pPqr2dg@mail.gmail.com>
On Sun, 9 Jun 2019 16:15:17 -0400
Noam Postavsky <npostavs@gmail.com> wrote:
> The thing containing the windows. See also (info "(emacs) Frames").
>
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Frames.html
I see. Although, without have read everything, and I'm certain there
are a lot of possibilities. it resumes itself for all practical
purposes much like another emacs instance, apart from sharing the same
underlying buffers.
In this case here, that M-x gdb shows the source code (gdb-main-window
non-nil) in another frame when the code starts running, while keeping
gdb interactive in the original frame, is the same as another instance.
Lost is the capability of seeing side-by-side gdb interactive and
source. Of course the new frame can be tailored to show both, but
what's the point in doing that every time gdb starts running code ?
This is why I prefer so far the fix that fixes this automatic frame
generation mentioned earlier. It enables free placement of buffers,
just like in regular single-frame emacs operation, while running gdb.
next prev parent reply other threads:[~2019-06-09 21:10 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
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 [this message]
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=20190609171036.18a89cb0@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).