From: tomas@tuxteam.de
To: Peng Yu <pengyu.ut@gmail.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: manpage of register_printf_specifier
Date: Sun, 28 Mar 2021 18:40:39 +0200 [thread overview]
Message-ID: <20210328164038.GE30897@tuxteam.de> (raw)
In-Reply-To: <20210328163234.GC30897@tuxteam.de>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On Sun, Mar 28, 2021 at 06:32:34PM +0200, tomas@tuxteam.de wrote:
> On Sun, Mar 28, 2021 at 11:24:28AM -0500, Peng Yu via Libc-help wrote:
> > Hi,
> >
> > I don't find the manpage of register_printf_specifier (I checked on
> > Linux). Is it available anywhere?
> >
> > I also checked a few other functions in printf.h. But I don't find
> > their manpages. Are the manpages of printf.h available?
>
> Hah. A friend of mine is working on one, AFAIK for the Linux documentation
> project. I was trying to free some time to translate it to info.
OK. More details:
- register_printf_function is, AFAIK an old interface and is
deprecated, although I'd double-check with people here, who
definitely know more than me.
That said, it's documented in the libc Info file, or, if
you prefer Web browsers, here:
https://www.gnu.org/software/libc/manual/html_node/Registering-New-Conversions.html
- these days one is supposed to use the pair register_printf_specifier,
register_printf_type; man pages, as I said, coming soon.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-03-28 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 16:24 Peng Yu
2021-03-28 16:32 ` tomas
2021-03-28 16:40 ` tomas [this message]
2021-03-29 3:59 ` Peng Yu
2021-03-29 8:08 ` Florian Weimer
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=20210328164038.GE30897@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=libc-help@sourceware.org \
--cc=pengyu.ut@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).