Re: [PATCH] printf.3: Document 'l' length modifier for a, A, e, E, f, F, g, and G

[Alejandro Colomar <alx.manpages@gmail.com>]

Hi Vincent,

On 5/20/22 16:10, Vincent Lefevre wrote:
> Signed-off-by: Vincent Lefevre <vincent@vinc17.net>
> ---
>   man3/printf.3 | 12 +++++++++++-
>   1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/man3/printf.3 b/man3/printf.3
> index 4fa1f11f3..63ea3092f 100644
> --- a/man3/printf.3
> +++ b/man3/printf.3
> @@ -502,7 +502,17 @@ argument, or a following
>   .B s
>   conversion corresponds to a pointer to
>   .I wchar_t
> -argument.
> +argument. In C99, on a following


Why "in C99"?  Is there a different meaning for non-C99?
Do we need to specify?

Also, see man-pages(7):

    Use semantic newlines
        In the source of a manual page, new sentences  should  be
        started on new lines, long sentences should be split into
        lines  at  clause breaks (commas, semicolons, colons, and
        so on), and long clauses should be split at phrase bound‐
        aries.  This convention,  sometimes  known  as  "semantic
        newlines",  makes it easier to see the effect of patches,
        which often operate at the level of individual sentences,
        clauses, or phrases.

Thanks,

Alex

> +.BR a ,
> +.BR A ,
> +.BR e ,
> +.BR E ,
> +.BR f ,
> +.BR F ,
> +.BR g ,
> +or
> +.B G
> +conversion, this length modifier is ignored.
>   .TP
>   .B ll
>   (ell-ell).

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/