From: Drew Adams <drew.adams@oracle.com>
To: "tomas@tuxteam.de" <tomas@tuxteam.de>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Calling a function with undefined symbol
Date: Tue, 1 Nov 2022 19:22:54 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488C56A6F0839538DC146EEF3369@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <Y2FFniaH1n5HEKTr@tuxteam.de>
> But you are right: a reference in the Elisp
> manual pointing to the Glossary in the Emacs
> manual seems like a good idea.
I didn't add a reference in the Elisp manual
point to the glossary in the Emacs manual.
(I didn't modify any manuals. My code just
works with the existing Emacs info files.)
I added the possibility (via user option) of
having occurrences of terms in the Elisp
manual (first occurrence in a topic, for each)
be linked to their entries in the Emacs manual.
___
Actually, there's a user option that lists
the manuals with glossaries to use, in order,
to link to. By default, only the Emacs and
the Semantics manuals are in that list, since
in the Emacs releases I have those are the
only manuals that have glossaries.
next prev parent reply other threads:[~2022-11-01 19:22 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:15 Calling a function with undefined symbol Heime
2022-10-31 8:32 ` Jean Abou Samra
2022-10-31 8:42 ` tomas
2022-10-31 8:57 ` Heime
2022-10-31 9:07 ` tomas
2022-10-31 9:24 ` Jean Abou Samra
2022-10-31 9:43 ` Heime
2022-10-31 9:58 ` Jean Abou Samra
2022-10-31 10:57 ` Heime
2022-10-31 17:00 ` [External] : " Drew Adams
2022-10-31 17:10 ` Emanuel Berg
2022-11-01 4:11 ` Drew Adams
2022-11-01 5:24 ` tomas
2022-11-01 15:58 ` Drew Adams
2022-11-01 16:13 ` tomas
2022-11-01 19:22 ` Drew Adams [this message]
2022-10-31 12:29 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-31 15:37 ` Emanuel Berg
2022-11-02 12:14 ` Michael Heerdegen
2022-11-02 14:25 ` Sam Steingold
2022-11-02 16:40 ` Michael Heerdegen
2022-11-02 17:28 ` Emanuel Berg
2022-11-02 23:04 ` Emanuel Berg
2022-11-03 11:09 ` Michael Heerdegen
2022-11-03 12:15 ` Emanuel Berg
2022-11-04 12:16 ` Michael Heerdegen
2022-11-05 14:32 ` Emanuel Berg
2022-11-05 23:22 ` Michael Heerdegen
2022-11-06 20:17 ` Emanuel Berg
2022-11-07 16:03 ` Michael Heerdegen
2022-11-07 16:50 ` [External] : " Drew Adams
2022-11-07 16:52 ` Emanuel Berg
2022-11-08 15:52 ` Michael Heerdegen
2022-11-08 19:15 ` tomas
2022-11-08 19:57 ` Michael Heerdegen
2022-11-08 20:47 ` tomas
2022-11-08 21:35 ` Sam Steingold
2022-11-08 23:53 ` Michael Heerdegen
2022-11-09 15:32 ` Sam Steingold
2022-11-09 15:59 ` Michael Heerdegen
2022-11-16 19:07 ` Emanuel Berg
2022-11-16 21:40 ` [External] : " Drew Adams
2022-11-16 21:55 ` Emanuel Berg
2022-11-04 14:33 ` Michael Heerdegen
2022-11-05 12:57 ` Emanuel Berg
2022-10-31 11:34 ` Emanuel Berg
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=SJ0PR10MB5488C56A6F0839538DC146EEF3369@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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).