unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: steve-humphreys@gmx.com
To: steve-humphreys@gmx.com
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Documentation about elisp code
Date: Sun, 2 May 2021 07:24:30 +0200	[thread overview]
Message-ID: <trinity-b50040d3-d46e-4281-a5b1-5c189abe3470-1619933070915@3c-app-mailcom-bs01> (raw)
In-Reply-To: <trinity-99beaa89-4230-4209-b5c8-853c17ccd23b-1619930040421@3c-app-mailcom-bs01>

Is there a way to call the documentation of another defun from the
in the doc-string using some sort of link?




> Sent: Sunday, May 02, 2021 at 4:34 PM
> From: steve-humphreys@gmx.com
> To: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Documentation about elisp code
>
>
> What would be a good strategy to use for displaying some documentation
> regarding some elisp code I have written.
>
> Naturally, I included documentation strings in my defuns.  But there
> is no information about learning the functionalities provided by my code.
> .
>
>
>
>
>
>
>



  reply	other threads:[~2021-05-02  5:24 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 [this message]
2021-05-02  6:58   ` Tassilo Horn
2021-05-02  7:48     ` steve-humphreys
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

  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=trinity-b50040d3-d46e-4281-a5b1-5c189abe3470-1619933070915@3c-app-mailcom-bs01 \
    --to=steve-humphreys@gmx.com \
    --cc=help-gnu-emacs@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. 
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).