From: Dave Abrahams <dave@boostpro.com>
To: emacs-devel@gnu.org
Subject: Plug-in debugger support for gud.el
Date: Thu, 28 Nov 2013 21:24:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20131128T221529-574@post.gmane.org> (raw)
I just rebased against HEAD the set of changes to gud.el that the LLDB project
created in 2010: http://j.mp/gud-lldb
I’d submit it, but I’m not the author of these changes and I suspect there
would be licensing problems. I also don’t love the idea of maintaining a
patchset to a standard emacs package.
So I was thinking, wouldn’t it be great if gud.el was factored in such a way
that debugger back-ends could be added as plug-ins? Then, presumably,
someone could maintain a smaller lldb.el package that, when loaded, adds
lldb support to gud.
Thoughts?
next reply other threads:[~2013-11-28 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 21:24 Dave Abrahams [this message]
2013-11-29 1:30 ` Plug-in debugger support for gud.el Stefan Monnier
2013-11-29 18:14 ` Dave Abrahams
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=loom.20131128T221529-574@post.gmane.org \
--to=dave@boostpro.com \
--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).