From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, Utkarsh Singh <utkarsh190601@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] printf.3: Add overall structure of format string
Date: Sun, 4 Apr 2021 21:32:26 +0200 [thread overview]
Message-ID: <bb1639ef-efa7-55b8-ad21-a334642099c4@gmail.com> (raw)
In-Reply-To: <20210319235717.28264-4-alx.manpages@gmail.com>
Hi Alex,
On 3/20/21 12:57 AM, Alejandro Colomar wrote:
> From: Utkarsh Singh <utkarsh190601@gmail.com>
>
> Can we add a small syntax structure for format string in printf(3)
> manual. I personally find if easier to remember and scan. This has
> been taken from OpenBSD printf(3) manual.
Patch applied.
Thanks,
Michael
> Signed-off-by: Utkarsh Singh <utkarsh190601@gmail.com>
> [ alx: ffix ]
> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> man3/printf.3 | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/man3/printf.3 b/man3/printf.3
> index fa6564426..7c993074c 100644
> --- a/man3/printf.3
> +++ b/man3/printf.3
> @@ -193,6 +193,14 @@ an optional
> and an optional
> .IR "length modifier" .
> .PP
> +Overall syntax of format string is:
> +.PP
> +.in +4n
> +.nf
> +%[$][flags][width][.precision][length modifier]conversion
> +.fi
> +.in
> +.PP
> The arguments must correspond properly (after type promotion) with the
> conversion specifier.
> By default, the arguments are used in the order
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2021-04-04 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 23:57 [PATCH] printf.3: Add overall structure of format string Alejandro Colomar
2021-04-04 19:32 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-08 8:15 [patch] " Utkarsh Singh
2021-03-10 19:42 ` Alejandro Colomar (man-pages)
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=bb1639ef-efa7-55b8-ad21-a334642099c4@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=utkarsh190601@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