From: David Kastrup <dak@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org
Subject: Re: RFC: a minor mode that uses GDB like CLI commands
Date: Mon, 21 Mar 2005 03:11:03 +0100 [thread overview]
Message-ID: <x5mzsx7npk.fsf@lola.goethe.zz> (raw)
In-Reply-To: <16958.14253.9851.210394@farnswood.snap.net.nz> (Nick Roberts's message of "Mon, 21 Mar 2005 14:55:40 +1200")
Nick Roberts <nickrob@snap.net.nz> writes:
> > It would be very good to make this mode to work like edebug
> > (automatically making the source code buffer read-only, etc.)
> > and to have similar keybindings:
> >
> > " " - step
> > "n" - next
> > "c" - cont
> > "g" - go
> > ...
>
> Its seems more natural to use the existing abbreviations for GDB, as Dan
> suggested:
>
> "s" - step
> "n" - next
> "c" - cont
> "r" - run
> "b" - break
> ...
>
> although there is clearly a significant overlap, in any case.
I think we should strive to make all of this as similar as possible,
so my take on it would be that we will, after the release of course,
change Edebug's bindings to match the bindings of gdb more closely, as
long as this works appropriately. Certainly the bindings of Edebug
and Gud-mode should be identical (if the rest of the user interface is
similar), and the bindings of Gud-mode and gdb itself as close as
feasible. I think we will meet less total opposition if we change
Edebug to match gdb more closely (where there are still discrepancies)
rather than the other way round...
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2005-03-21 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 18:58 RFC: a minor mode that uses GDB like CLI commands Dan Nicolaescu
2005-03-19 1:28 ` Miles Bader
2005-03-19 12:32 ` Juri Linkov
2005-03-21 2:55 ` Nick Roberts
2005-03-21 2:11 ` David Kastrup [this message]
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=x5mzsx7npk.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.