From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: [PATCH] newlib: docs: print the function index
Date: Fri, 5 Jan 2024 00:00:56 -0500 [thread overview]
Message-ID: <20240105050056.26457-1-vapier@gentoo.org> (raw)
The generated function documentation makes sure to include entries for
every function in the function index via @findex, but then the manuals
forget to actually print the index.
---
newlib/libc/libc.texi | 4 ++++
newlib/libm/libm.texi | 5 +++++
2 files changed, 9 insertions(+)
diff --git a/newlib/libc/libc.texi b/newlib/libc/libc.texi
index c6aeab2278f1..ea96f86b6e3f 100644
--- a/newlib/libc/libc.texi
+++ b/newlib/libc/libc.texi
@@ -410,6 +410,10 @@ usage as the ANSI C version from @file{stdarg.h}.
@unnumbered Document Index
@printindex cp
+@node Function Index
+@unnumbered Function Index
+@printindex fn
+
@tex
% I think something like @@colophon should be in texinfo. In the
% meantime:
diff --git a/newlib/libm/libm.texi b/newlib/libm/libm.texi
index 943262d055ae..26c393df8c6b 100644
--- a/newlib/libm/libm.texi
+++ b/newlib/libm/libm.texi
@@ -121,10 +121,15 @@ This makes it thread safe, and therefore reentrant.
Currently, the full set of long double math functions is only provided
on platforms where long double equals double.
For such platforms, the long double math functions are implemented as calls to the double versions.
+
@node Document Index
@unnumbered Document Index
@printindex cp
+@node Function Index
+@unnumbered Function Index
+@printindex fn
+
@tex
% I think something like @@colophon should be in texinfo. In the
% meantime:
--
2.43.0
next reply other threads:[~2024-01-05 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 5:00 Mike Frysinger [this message]
2024-01-05 5:09 ` [PATCH v2] " Mike Frysinger
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=20240105050056.26457-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.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).