unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: 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 14:55:40 +1200	[thread overview]
Message-ID: <16958.14253.9851.210394@farnswood.snap.net.nz> (raw)
In-Reply-To: <87sm2rol04.fsf@jurta.org>

 > 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 the idea of making the debugger source based is a good one and has
been tried with gdbsrc.el in XEmacs. The difficulty lies in ensuring that any
such mode does not interfere with the normal editing process. As it is
proposed, the user would need to keep track of buffers where it was turned on
and those where it was turned off. That is why I suggested to Dan that it
might be better to toggle all the buffers at once. This is not easy with the
present version of gdb-ui, but can be done using the features of GDB 6.2 that I
described in relation to turning on gud-minor-mode for existing buffers. It is
then possible to define a variable gdb-source-file-list which contains all the
source files for the current executable. This list could also be used to
toggle gdb-src-cmd-minor-mode.


Nick

  reply	other threads:[~2005-03-21  2:55 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 [this message]
2005-03-21  2:11     ` David Kastrup

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=16958.14253.9851.210394@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=dann@ics.uci.edu \
    --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).