Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com
Subject: Re: Emacs section of Gdb Manual
Date: Fri, 13 Jun 2003 20:36:00 -0000	[thread overview]
Message-ID: <vt21xxxsoid.fsf@zenia.home> (raw)
In-Reply-To: <16105.5179.107976.322438@nick.uklinux.net>

Nick Roberts <nick@nick.uklinux.net> writes:

> With the imminent release of GDB version 6, I thought I'd point out
> that much of the Emacs page of Gdb Manual is out of date or wrong:
> 
> M-s should read C-c C-s
> M-n should read C-c C-n
> M-i should read C-c C-i
> There is no gdb-nexti (or even gud-nexti in a released version of Emacs)
> M-c should read C-c C-r
> M-u should read C-c <
> M-d should read C-c >
> There are references to Emacs 19 (current version is 21)
> C-x & is not defined and the description that follows is no longer
> relevant (AFAIK)
> `C-x SPC' is gud-break not gdb-break
> etc
> 
> It could be updated but as the Emacs manual has a relevant section 
> (Emacs-> Building-> Debuggers) and its interaction with Gdb is evolving,
> I suggest that the Gdb manual refers to this section.
> 
> I will be happy to rewrite/update this page if anyone wishes.

Yeah, a patch to bring it up to date would be greatly appreciated.


  parent reply	other threads:[~2003-06-13 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13  0:06 Nick Roberts
2003-06-13 13:36 ` Daniel Jacobowitz
2003-06-14  7:45   ` Eli Zaretskii
2003-06-13 20:36 ` Jim Blandy [this message]
2003-06-15  2:33 ` Andrew Cagney
2003-06-15  3:37   ` Eli Zaretskii
2003-06-15 12:36     ` Andrew Cagney
2003-06-15 15:52       ` Eli Zaretskii
2003-06-15 21:28       ` Nick Roberts
2003-06-16  4:06         ` Eli Zaretskii
2003-06-15 21:28   ` Nick Roberts
2003-06-16  4:08     ` Eli Zaretskii

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=vt21xxxsoid.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox