From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How does `describe-function' know where the source code of the function is?
Date: Mon, 17 Jan 2022 21:51:58 -0500 [thread overview]
Message-ID: <jwviluheozl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87pmorf1p5.fsf@mbork.pl
> question is: how does `describe-function' know where the link should
> point to (and if it should be rendered at all)? I skimmed its source
The name of the file is stored in `load-history`. The function
definition itself is then found (or not) by a naive regexp search.
Stefan
next prev parent reply other threads:[~2022-01-18 2:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 4:03 How does `describe-function' know where the source code of the function is? Marcin Borkowski
2022-01-17 4:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-17 4:27 ` Eduardo Ochs
2022-01-17 16:22 ` Michael Heerdegen
2022-01-18 2:51 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-01-18 17:41 ` Marcin Borkowski
2022-01-18 18:46 ` 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
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=jwviluheozl.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).