From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Rocky Bernstein <rocky@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Grand Unified Debugger Rewrite's process buffer: comint, eterm or
Date: Mon, 02 Nov 2009 10:25:05 -0500 [thread overview]
Message-ID: <jwvvdhv70o5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6cd6de210910301730x5c46347bn9e098f572b62a512@mail.gmail.com> (Rocky Bernstein's message of "Fri, 30 Oct 2009 20:30:41 -0400")
>> > I have started to rewrite gud from the ground up.
>> That's interesting. I hope you will start with the assumption that
>> there are several active GUD sessions (each using potentially different
>> debuggers for different languages). It's a kind of change that's
>> difficult to make after the fact, but that's fairly easy to build-in
>> from the beginning.
> Yep.
Good, thank you.
> [..digression/rant..]
Glad to here it.
>> > 1. I can stick with comint.el. It seems the most creaky.
>> > 2. term.el is pretty cool, but it doesn't provide a hook to run when
>> > output is produced and this is something I need. I use it both in
>> > comint.el and eshell.el in "shell tracker" (think pdb-track) mode. So
>> > this leads to the last choice ...
>>
>> In order to make a choice, I think we need to know what problems we're
>> trying to address.
>>
> Perhaps some of this is addressed above.
Not at all. The apparently relevant issues have to do with whether or
not you need a terminal emumlation and things like that.
My recommendation: stick to comint.
Stefan
next prev parent reply other threads:[~2009-11-02 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 15:48 Grand Unified Debugger Rewrite's process buffer: comint, eterm or eshell? Rocky Bernstein
2009-10-30 19:19 ` Grand Unified Debugger Rewrite's process buffer: comint, eterm or Stefan Monnier
2009-10-31 0:30 ` Rocky Bernstein
2009-11-02 15:25 ` Stefan Monnier [this message]
2009-10-31 5:51 ` Grand Unified Debugger Rewrite's process buffer: comint, eterm or eshell? Miles Bader
2009-11-01 15:08 ` Rocky Bernstein
2009-11-06 16:57 ` Dan Nicolaescu
2009-11-06 17:16 ` Rocky Bernstein
2009-11-06 21:49 ` Nick Roberts
2009-11-07 0:22 ` Rocky Bernstein
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=jwvvdhv70o5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rocky@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 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.