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: Set Cross-Reference to Emacs Function Descriptor in Info Documentation
Date: Mon, 19 Oct 2020 11:36:51 +0200 [thread overview]
Message-ID: <87eelu4kwc.fsf@ebih.ebihd> (raw)
In-Reply-To: trinity-e7d5a3cd-213f-4b64-a552-36ada89211d4-1603094938914@3c-app-mailcom-bs06
Christopher Dimech wrote:
> I am writing an abbreviated documentation for Elisp
...
> When writing a manual, is it possible to introduce
> a link to a documentation of a function such as
> "interactive" so the user can see displayed as
> though he has pressed "M-x describe-function <Ret>
> interactive <Ret>".
It depends what format the document is...
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-10-19 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 8:08 Set Cross-Reference to Emacs Function Descriptor in Info Documentation Christopher Dimech
2020-10-19 9:36 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-10-19 10:51 ` Christopher Dimech
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=87eelu4kwc.fsf@ebih.ebihd \
--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).