unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:59:56 +0200	[thread overview]
Message-ID: <83r0v9z5gz.fsf@gnu.org> (raw)
In-Reply-To: <87edr9qwz8.fsf@md5i.com> (message from Michael Welsh Duggan on Wed, 01 Feb 2023 09:30:35 -0500)

> From: Michael Welsh Duggan <mwd@md5i.com>
> Cc: Michael Welsh Duggan <mwd@md5i.com>,  61162@debbugs.gnu.org
> Date: Wed, 01 Feb 2023 09:30:35 -0500
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.
> 
> Ah, I remember now.  It was the ability to debug the same program twice
> at once that was lacking.  I haven't needed that ability recently.  (I
> needed it in the past when dealing with a program that connected to
> other instances of itself.)

Are you sure you cannot have this if you manually rename one of the
GUD buffers?





      reply	other threads:[~2023-02-01 16:59 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
2023-02-01 14:30         ` Michael Welsh Duggan
2023-02-01 16:59           ` Eli Zaretskii [this message]

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=83r0v9z5gz.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 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).