.gdbinit

.gdbinit

[Eli Zaretskii]

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.

Re: .gdbinit

[Kim F. Storm]

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

Re: .gdbinit

[Eli Zaretskii]

> Cc: emacs-devel@gnu.org
> From: storm@cua.dk (Kim F. Storm)
> Date: Fri, 23 Jun 2006 16:35:53 +0200
> 
> 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.

Thank you.  I added a pointer to that description near the beginning
of the file.

Re: .gdbinit

[Nick Roberts]

Eli Zaretskii writes:
 > > Cc: emacs-devel@gnu.org
 > > From: storm@cua.dk (Kim F. Storm)
 > > Date: Fri, 23 Jun 2006 16:35:53 +0200
 > > 
 > > 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.
 > 
 > Thank you.  I added a pointer to that description near the beginning
 > of the file.

Following on from what Eli said in his first post, I think that it would be a
good idea at some stage to put DEBUG into the Elisp manual assuming that size
isn't an issue.  The references to other manuals could then be made into
hyperlinks.


-- 
Nick                                           http://www.inet.net.nz/~nickrob