From: steve-humphreys@gmx.com
To: Tassilo Horn <tsdh@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Documentation about elisp code
Date: Sun, 2 May 2021 09:48:38 +0200 [thread overview]
Message-ID: <trinity-0d48b31d-b901-44ca-9cef-a9174ef9315f-1619941718837@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87pmy9vctv.fsf@gnu.org>
Have tried your suggestion, but the funtion is not clickable
(defun guide ()
"`guidance-ediff'"
(message "guide") )
> Sent: Sunday, May 02, 2021 at 6:58 PM
> From: "Tassilo Horn" <tsdh@gnu.org>
> To: steve-humphreys@gmx.com
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Documentation about elisp code
>
> steve-humphreys@gmx.com writes:
>
> > Is there a way to call the documentation of another defun from the
> > in the doc-string using some sort of link?
>
> When your docstring contains `some-other-function-or-var' (with this
> quoting), it'll be a clickable link in the *Help* buffer. And `C-h f'
> and `C-h v' will also suggest that as default when point is on that
> symbol.
>
> Bye,
> Tassilo
>
>
next prev parent reply other threads:[~2021-05-02 7:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 4:34 Documentation about elisp code steve-humphreys
2021-05-02 5:24 ` steve-humphreys
2021-05-02 6:58 ` Tassilo Horn
2021-05-02 7:48 ` steve-humphreys [this message]
2021-05-02 8:21 ` Tassilo Horn
2021-05-02 9:07 ` steve-humphreys
2021-05-02 10:25 ` steve-humphreys
2021-05-02 10:40 ` tomas
2021-05-02 10:55 ` steve-humphreys
2021-05-02 17:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-02 23:10 ` [External] : " Drew Adams
2021-05-02 5:31 ` Jean Louis
2021-05-02 6:11 ` steve-humphreys
2021-05-02 9:08 ` Nikolay Kudryavtsev
2021-05-02 10:21 ` steve-humphreys
2021-05-02 17:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-02 7:22 ` Eli Zaretskii
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=trinity-0d48b31d-b901-44ca-9cef-a9174ef9315f-1619941718837@3c-app-mailcom-bs01 \
--to=steve-humphreys@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tsdh@gnu.org \
/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.