From: Stefan Puiu <stefan.puiu@gmail.com>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
lnx-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] printf.3: Document 'l' length modifier for a, A, e, E, f, F, g, and G
Date: Tue, 24 May 2022 10:07:43 +0300 [thread overview]
Message-ID: <CACKs7VAsrEzneeu84quRvw5cRcio-j2rAWyHvQTNZf6_5CqWtg@mail.gmail.com> (raw)
In-Reply-To: <20220520173043.GC1112518@zira.vinc17.org>
Hi Vincent,
On Sat, May 21, 2022 at 8:33 AM Vincent Lefevre <vincent@vinc17.net> wrote:
>
> Signed-off-by: Vincent Lefevre <vincent@vinc17.net>
> ---
> man3/printf.3 | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/man3/printf.3 b/man3/printf.3
> index 4fa1f11f3..a231d626c 100644
> --- a/man3/printf.3
> +++ b/man3/printf.3
> @@ -503,6 +503,17 @@ argument, or a following
> conversion corresponds to a pointer to
> .I wchar_t
> argument.
> +On a following
> +.BR a ,
> +.BR A ,
> +.BR e ,
> +.BR E ,
> +.BR f ,
> +.BR F ,
> +.BR g ,
> +or
> +.B G
> +conversion, this length modifier is ignored (C99; not in SUSv2).
I'm not a native English speaker, but I think "Following a ...
conversion" sounds better, unless I misunderstand the phrase.
My 2 cents,
Stefan.
> .TP
> .B ll
> (ell-ell).
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-05-24 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 14:10 [PATCH] printf.3: Document 'l' length modifier for a, A, e, E, f, F, g, and G Vincent Lefevre
2022-05-20 14:44 ` Alejandro Colomar
2022-05-20 16:11 ` Vincent Lefevre
2022-05-20 16:18 ` Alejandro Colomar
2022-05-20 17:30 ` Vincent Lefevre
2022-05-21 17:17 ` Alejandro Colomar
2022-05-24 7:07 ` Stefan Puiu [this message]
2022-05-24 7:39 ` Vincent Lefevre
2022-05-24 12:23 ` Stefan Puiu
2022-05-24 13:57 ` Vincent Lefevre
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=CACKs7VAsrEzneeu84quRvw5cRcio-j2rAWyHvQTNZf6_5CqWtg@mail.gmail.com \
--to=stefan.puiu@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=vincent@vinc17.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.