From: LemonBreezes <look@strawberrytea.xyz>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: 64914@debbugs.gnu.org
Subject: bug#64914: [PATCH] * gdb-mi.el: allow disabling the gdb io buffer
Date: Fri, 28 Jul 2023 10:54:02 -0400 [thread overview]
Message-ID: <65da37ba-9f1e-4f42-8a27-2f7b0f60c700@app.fastmail.com> (raw)
In-Reply-To: <83mszgjnf7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
No, setting gdb-display-io-nopopup to nil does not prevent the program IO from being split off into the gdb-inferior-io buffer, nor does it prevent the gdb-inferior-io buffer from popping up when debugging is started. The purpose of setting gdb-display-io-buffer to nil is to prevent the gdb-inferior-io buffer from being created altogether, instead outputting the program output to the GDB buffer itself. A user in the Doom Emacs Discord told me this used to be the behavior of gdb-mi.el but that it was changed without giving the user the option to opt out. I have not investigated that but the comments say that is a feature of GDB 6.4 onward.
On Fri, Jul 28, 2023, at 7:17 AM, Eli Zaretskii wrote:
> > From: StrawberryTea <look@strawberrytea.xyz>
> > Date: Thu, 27 Jul 2023 20:33:39 -0400
> >
> > This change allows the user to disable the `gdb-inferior-io' buffer.
> > This is useful for users that prefer a more classical gdb experience
> > where you just have the GDB window and the source window.
>
> Sorry, I don't think I understand why you need a new defcustom.
> Doesn't setting gdb-display-io-nopopup non-nil already achieve what
> you want? It does here.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1681 bytes --]
next prev parent reply other threads:[~2023-07-28 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 0:33 bug#64914: [PATCH] * gdb-mi.el: allow disabling the gdb io buffer StrawberryTea
2023-07-28 11:17 ` Eli Zaretskii
2023-07-28 14:54 ` LemonBreezes [this message]
2023-07-28 15:48 ` Eli Zaretskii
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=65da37ba-9f1e-4f42-8a27-2f7b0f60c700@app.fastmail.com \
--to=look@strawberrytea.xyz \
--cc=64914@debbugs.gnu.org \
--cc=eliz@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).