From: "R. Bernstein" <rocky@panix.com>
Subject: Re: gud.el organization and adding debuggers
Date: Thu, 2 Feb 2006 17:50:23 -0500 [thread overview]
Message-ID: <17378.36015.450470.209995@panix3.panix.com> (raw)
In-Reply-To: <m164nyl4yt.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> 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. And
if I want to debug the same program more than once simultaneously a
"rename-buffer" or "rename-uniquely" works for me.
> Patches welcome.
You *did* read the part where I wrote:
I'm not a GNU-Emacs wizard, ...
again, I'm not a wizard).
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".
However when it gets to stuff like this:
> I think a good first step would be to kill gud-def.
> Instead of gud sub-modes using
...
you are out of my league. I don't really understand what you are
talking about. If you really think this is the way to go, you may be
the best candidate for doing it. ;-)
next prev parent reply other threads:[~2006-02-02 22:50 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 [this message]
2006-02-03 2:30 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17378.36015.450470.209995@panix3.panix.com \
--to=rocky@panix.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.