From: "Drew Adams" <drew.adams@oracle.com>
Subject: Help cross reference to source file
Date: Sat, 8 Jul 2006 18:35:52 -0700 [thread overview]
Message-ID: <MEEKKIABFKKDFJMPIOEBEEPJDCAA.drew.adams@oracle.com> (raw)
I have a macro that I use to define functions; that is, it expands to and
evaluates a defun. Suppose that I use the macro in file `foo.el' to define
function `fun'. If I then do C-h f fun, I see this in *Help*:
fun is an interactive compiled Lisp function in `foo.el'.
The library name foo.el is a link here. However, if I click the link, I get
an error message:
Cannot find definition of `fun' in library `foo.el'
Fair enough; help can't know where the function definition is, though it is
able to identify the file.
Even if help can't take me to the right place in the source file, I think it
should open the file - and provide the error message, inviting me to search
for it in the file.
This would be analogous to what we do when Emacs cannot find the source C
file that defines a built-in - at least on Windows, it opens a file dialog
box that lets you navigate to the source file.
I think it's great that the source file is identified (correctly), and it's
good that the file name is a link. However, if the definition cannot be
located in the file, the file should be opened, and then a message can say
that the definition can't be located.
next reply other threads:[~2006-07-09 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 1:35 Drew Adams [this message]
2006-07-09 19:04 ` Help cross reference to source file Richard Stallman
2006-07-09 19:55 ` Drew Adams
2006-07-10 16:41 ` Stefan Monnier
2006-07-10 17:48 ` Drew Adams
2006-07-11 4:29 ` Stefan Monnier
2006-07-11 18:16 ` Richard Stallman
2006-07-11 5:51 ` Richard Stallman
2006-07-11 18:14 ` Drew Adams
2006-07-12 15:36 ` Richard Stallman
2006-07-11 5:51 ` Richard Stallman
2006-07-11 12:14 ` Stefan Monnier
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=MEEKKIABFKKDFJMPIOEBEEPJDCAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.