all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: steve-humphreys@gmx.com
To: Jean Louis <bugs@gnu.support>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Documentation about elisp code
Date: Sun, 2 May 2021 08:11:50 +0200	[thread overview]
Message-ID: <trinity-69019737-b39e-4e2a-a837-a3ce2ed0956f-1619935910554@3c-app-mailcom-bs01> (raw)
In-Reply-To: <YI45Hm42TGc2WvrZ@protected.localdomain>

I have coded so much stuff that I hardly remember what capabilities
exist.  Would really like to access an abbreviated documentation
inside emacs, whilst I am hacking at things.  Using manual online,
or a pdf (etc) is very  inconvenient.

I quite like the idea of using something similar to

(info "(elisp) Packaging")

For instance

(info "(myelisp) Topic")

Is there a way for such functionality?



> Sent: Sunday, May 02, 2021 at 5:31 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: steve-humphreys@gmx.com
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Documentation about elisp code
>
> * steve-humphreys@gmx.com <steve-humphreys@gmx.com> [2021-05-02 07:34]:
> > 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.
>
> I recommend reading about: (info "(elisp) Packaging")
>
> There are few ways to document it:
>
> - document it inline in documentation strings and if necessary in the
>   Commentary section inside of a package;
>
> - or create multi file package and use either README or info file or
>   other file to document it; best would be info if documentation is
>   important;
>
>
>
> --
> Jean
>
> Take action in Free Software Foundation campaigns:
> https://www.fsf.org/campaigns
>
> Sign an open letter in support of Richard M. Stallman
> https://stallmansupport.org/
> https://rms-support-letter.github.io/
>
>
>



  reply	other threads:[~2021-05-02  6:11 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
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 [this message]
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-69019737-b39e-4e2a-a837-a3ce2ed0956f-1619935910554@3c-app-mailcom-bs01 \
    --to=steve-humphreys@gmx.com \
    --cc=bugs@gnu.support \
    --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.
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.