From: Eli Zaretskii <eliz@gnu.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: 61162@debbugs.gnu.org
Subject: bug#61162: 30.0.50; RET in source files that are being displayed by gud no longer works
Date: Wed, 01 Feb 2023 15:18:21 +0200 [thread overview]
Message-ID: <83y1phzfqa.fsf@gnu.org> (raw)
In-Reply-To: <87sffqqwzc.fsf@md5i.com> (message from Michael Welsh Duggan on Tue, 31 Jan 2023 15:18:15 -0500)
> From: Michael Welsh Duggan <mwd@md5i.com>
> Cc: Michael Welsh Duggan <mwd@md5i.com>, 61162@debbugs.gnu.org
> Date: Tue, 31 Jan 2023 15:18:15 -0500
>
> > If you can find a fix on master, patches would be very welcome.
> > Failing that, I might eventually decide to revert that commit on
> > master as well. There's a limit to the efforts I'm prepared to sink
> > into maintaining what is basically an obsolete package which uses a
> > GDB feature that GDB developers consider obsolete and may remove any
> > day (why don't you use "M-x gdb" instead?).
>
> I always use "M-x gud-gdb" because, historically, "M-x gdb" didn't
> support multiple simultaneous gdb sessions. If this is no longer the
> case, I will see if I can change my habits.
This is no longer the case, if it ever was. What exactly didn't work
for you when you tried several simultaneous sessions? The buffer
where you type GDB commands is named "*gud-PROGRAM*", so you have
separate buffers for different sessions. And if you start each one
from a separate Emacs frame, you should be able to have separate
multi-window configurations (see gdb-many-windows) for each session.
next prev parent reply other threads:[~2023-02-01 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 2:07 bug#61162: 30.0.50; RET in source files that are being displayed by gud no longer works Michael Welsh Duggan
2023-01-31 19:17 ` Michael Welsh Duggan
2023-01-31 19:53 ` Eli Zaretskii
2023-01-31 20:18 ` Michael Welsh Duggan
2023-02-01 13:18 ` Eli Zaretskii [this message]
2023-02-01 14:30 ` Michael Welsh Duggan
2023-02-01 16:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1phzfqa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61162@debbugs.gnu.org \
--cc=mwd@md5i.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.