From: jonetsu <jonetsu@teksavvy.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Using gdb (windows popping up)
Date: Sun, 9 Jun 2019 12:58:08 -0400 [thread overview]
Message-ID: <20190609125808.58e94436@mistral> (raw)
In-Reply-To: <20190609121823.5192ecd2@mistral>
On Sun, 9 Jun 2019 12:18:23 -0400
jonetsu <jonetsu@teksavvy.com> wrote:
> ... Until the debugged app outputs something. Then yes, the problem
> with a new emacs instance popping is solved, but emacs insists on
> replacing the source code with the output window.
Found out that this is solved by setting the following variable to
non-nil (default is nil) :
gdb-display-io-nopopup
Also saw that there are incredible people with lots of patience, as
this Stack Exchange post on this topic shows, with the subject:
"How can I prevent gdb *input/output* buffer from aggressively popping
up in frame?"
The above solution is presented and the reply was:
"Thank you, thank you, thank you! This has been an irritation for me for
years!"
I mean, years ? I couldn't stand it for a day ! :)
next prev parent reply other threads:[~2019-06-09 16:58 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 [this message]
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=20190609125808.58e94436@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).