From: steve-humphreys@gmx.com
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>, Jean Louis <bugs@gnu.support>
Subject: Re: Documentation about elisp code
Date: Sun, 2 May 2021 12:21:45 +0200 [thread overview]
Message-ID: <trinity-31f4bb54-7ee0-4293-b6ba-da596307f911-1619950905429@3c-app-mailcom-bs01> (raw)
In-Reply-To: <1309c15d-aa51-a7d8-da27-122e11335ba3@gmail.com>
> Sent: Sunday, May 02, 2021 at 9:08 PM
> From: "Nikolay Kudryavtsev" <nikolay.kudryavtsev@gmail.com>
> To: steve-humphreys@gmx.com, "Jean Louis" <bugs@gnu.support>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Documentation about elisp code
>
> (info "(myelisp) Topic") just finds "Topic" in "myelisp" info manual. So if you write that manual and get it to install for the user(generally done by distributing your code through package.el) it would work.
>
> Apart from everything suggested previously there's also an option of writing a custom help command, which user can quickly open with a hotkey. Some beefier pacakges do that, like Helm and Icicles.
Thanks, I am checking helm. Thanks for the hints.
next prev parent reply other threads:[~2021-05-02 10:21 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
2021-05-02 9:08 ` Nikolay Kudryavtsev
2021-05-02 10:21 ` steve-humphreys [this message]
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-31f4bb54-7ee0-4293-b6ba-da596307f911-1619950905429@3c-app-mailcom-bs01 \
--to=steve-humphreys@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=nikolay.kudryavtsev@gmail.com \
/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).