From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: .gdbinit
Date: Fri, 23 Jun 2006 16:35:53 +0200 [thread overview]
Message-ID: <m33bdwq6ra.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <uodwk9fus.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Jun 2006 16:11:23 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> The file .gdbinit has such a large amount of useful commands that it
> probably justifies a section in some manual, perhaps an appendix to
> the ELisp manual. At the very least, we should have a text file
> etc/SOMETHING which describes those commands and gives some advice
> when to use them.
I have added some information to etc/DEBUG.
Please have a look.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-06-23 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 13:11 .gdbinit Eli Zaretskii
2006-06-23 14:35 ` Kim F. Storm [this message]
2006-06-23 18:15 ` .gdbinit Eli Zaretskii
2006-06-23 22:03 ` .gdbinit Nick Roberts
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=m33bdwq6ra.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).