unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg 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 05:14:20 +0100	[thread overview]
Message-ID: <87o84b9exv.fsf@zoho.eu> (raw)
In-Reply-To: 87pmorf1p5.fsf@mbork.pl

Marcin Borkowski wrote:

> If I define a function with `defun', C-h f gives me a link
> to the source code of the function. I defined a macro
> defining a function (its expansion contained a `defun'), and
> C-h f'ing that function did /not/ give me that link. I tried
> saying M-: (symbol-plist 'my-function), but I haven't seen
> any property that would point to the source code. So, my
> question is: how does `describe-function' know where the
> link should point to (and if it should be rendered at all)?

Isn't the help system fed data when the defun is evaluated?

After that it's too late to find out :)

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-01-17  4:14 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 [this message]
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
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=87o84b9exv.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).