all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Rocky Bernstein <rocky@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Grand Unified Debugger Rewrite's process buffer: comint, eterm or  eshell?
Date: Fri, 6 Nov 2009 08:57:00 -0800 (PST)	[thread overview]
Message-ID: <200911061657.nA6Gv0uP027422@godzilla.ics.uci.edu> (raw)
In-Reply-To: <6cd6de210910300848g69755d4bx98366d5f4ed90705@mail.gmail.com> (Rocky Bernstein's message of "Fri, 30 Oct 2009 11:48:20 -0400")

Rocky Bernstein <rocky@gnu.org> writes:

  > I have started to rewrite gud from the ground up.

Another thing you might want to consider in the design is to allow
debugger interaction with simple key bindings from file buffers.  

Now to send commands to the debugger you'd have to use the *gud* buffer,
or use complicated key bindings.  
Compare to how `edebug' works, the buffer is made read-only, and simple
bindings like: n c d  can be used.




  parent reply	other threads:[~2009-11-06 16:57 UTC|newest]

Thread overview: 14+ 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
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 [this message]
2009-11-06 17:16   ` Rocky Bernstein
2009-11-06 21:49   ` Nick Roberts
2009-11-07  0:22     ` Rocky Bernstein
  -- strict thread matches above, loose matches on Subject: below --
2009-10-30 14:32 rocky
2009-11-01 21:30 ` Dave Love
2009-11-02 14:44   ` rocky
2009-11-02 14:59   ` Tom Tromey

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=200911061657.nA6Gv0uP027422@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --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.