From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 67928@debbugs.gnu.org
Subject: bug#67928: 30.0.50; [PATCH] Load GDB history in gud-gdb
Date: Wed, 20 Dec 2023 16:47:13 +0200 [thread overview]
Message-ID: <83h6kdgccu.fsf@gnu.org> (raw)
In-Reply-To: <87sf3x7z3i.fsf@ledu-giraud.fr> (message from Manuel Giraud on Wed, 20 Dec 2023 15:00:49 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: 67928@debbugs.gnu.org
> Date: Wed, 20 Dec 2023 15:00:49 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Wed, 20 Dec 2023 13:43:23 +0100
> >> From: Manuel Giraud via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >>
> >> 'M-x gud-gdb' does not load GDB history by default. This patch fixes
> >> this.
> >
> > Thanks, but why should we enhance gud-gdb? It is based on a
> > deprecated GDB feature (annotations), which the GDB developers may
> > remove some day without any advance warning. It is basically kept in
> > Emacs as a fallback, for those who for some reasons cannot use gdb-mi.
> > And gdb-mi already loads the history.
> >
> > Are there any reasons for you to use gud-gdb?
>
> I have set 'gdb-many-windows' to 't' but sometimes I like the simpler
> version provided by gud-gdb... But yes, this reason is not sufficient.
> Before closing this PR, could I modify this patch to, at least, isolate
> history loading into its own function?
Yes, that's fine.
next prev parent reply other threads:[~2023-12-20 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 12:43 bug#67928: 30.0.50; [PATCH] Load GDB history in gud-gdb Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-20 13:28 ` Eli Zaretskii
2023-12-20 14:00 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-20 14:47 ` Eli Zaretskii [this message]
2023-12-20 16:41 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-21 11:52 ` 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=83h6kdgccu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67928@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).