From: Nick Roberts <nickrob@snap.net.nz>
To: Juanma <juanma_bellon@yahoo.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Mode for files visited by GUD
Date: Thu, 17 Jul 2008 12:13:34 +1200 [thread overview]
Message-ID: <18558.36526.630474.990664@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200807170135.53892.juanma_bellon@yahoo.es>
> Is there any mode (and it's hook) run when GUD visits a source code file
> during debugging?
gdb-find-file-hook is run when GUD visits a source code file. You could
advise that function or create your own hook using find-file-hook
(see the Elisp manual).
> I have found a gud-minor-mode variable, but it's not documented. Anyway,
> quickly peeping into the source, it doesn't seem like that minor mode would
> serve my purpose.
Not all variables are documented, particularly those for internal use.
gud-minor-mode is probably such a variable.
> Actually, many functions and variables are not documented. I'm not helping,
> so I'm not complaining. I'm just curious, because I find it odd for a mature
> package (GUD has gone along with Emacs since a very long time ago, right?)
> to have many things left undocumented.
Documentation is provided at the user level in the Emacs and Elisp manuals and
through the documentaion strings. And there are comments in the source code to
help developers. It's a question of balancing convenience with overhead. Also
comment/doc strings can get out of date and sometimes it's better to let the
code speak for itself.
> BTW, is Emacs' CVS repository, under emacs/lisp/progmodes, the right place to
> find the latest version?
Yes, but to ensure it always works, you really need to check out all of Emacs
from the repository, and then you can update when fixes are made.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-07-17 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 23:35 Mode for files visited by GUD Juanma
2008-07-17 0:13 ` Nick Roberts [this message]
2008-07-17 23:54 ` Juanma
2008-07-18 0:21 ` Juanma
2008-07-18 0:30 ` Nick Roberts
2008-07-18 1:08 ` Juanma
2008-07-18 1:32 ` Nick Roberts
2008-07-19 1:40 ` Juanma
2008-07-19 2:20 ` 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=18558.36526.630474.990664@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=help-gnu-emacs@gnu.org \
--cc=juanma_bellon@yahoo.es \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).