From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: gud.el organization and adding debuggers
Date: Thu, 02 Feb 2006 21:30:22 -0500 [thread overview]
Message-ID: <87d5i5npmn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <17378.36015.450470.209995@panix3.panix.com> (R. Bernstein's message of "Thu, 2 Feb 2006 17:50:23 -0500")
>> Yes, GUD's support for particular debuggers should be made more modular.
>> It should also be possible to have several GUD sessions using different
>> debuggers at the same time.
> Huh? Currently I have have no problem having several GUD sessions.
Really? And those GUD sessions don't all use the same debugger?
Which debuggers do they use?
> And if I want to debug the same program more than once simultaneously
> a "rename-buffer" or "rename-uniquely" works for me.
The problem is (among a few others) that each sessions makes global changes.
E.g. `gud-def' redefines globally the text sent to the underlying debuggers.
> However, if there seems to be a consensus on this, I'd be happy to
> break gud.el into a generic file (gud.el) and several
> debugger-specific files (bashdb.el, mdb.el, pydb.el, etc.). Also make
> the changes I suggested in my previous email of using "define-key
> gud-menu-map" and removing entries from "easy-mmode-defmap
> gud-menu-map".
I'd rather keep as many entries in gud-menu-map as possible, and simply make
them invisible when the debugger doesn't support them. This will ensure
better consistency between the various debuggers supported.
Stefan
next prev parent reply other threads:[~2006-02-03 2:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 0:57 gud.el organization and adding debuggers R. Bernstein
2006-02-02 5:30 ` Stefan Monnier
2006-02-02 22:50 ` R. Bernstein
2006-02-03 2:30 ` Stefan Monnier [this message]
2006-02-03 4:08 ` R. Bernstein
2006-02-03 4:34 ` Stefan Monnier
2006-02-05 7:44 ` Nick Roberts
2006-02-05 7:44 ` Nick Roberts
[not found] <20060205174024.2BCBB9DB3E@mail2.panix.com>
2006-02-06 3:02 ` R. Bernstein
2006-02-06 5:07 ` Nick Roberts
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=87d5i5npmn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).