All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent@vinc17.net>
To: Stefan Puiu <stefan.puiu@gmail.com>
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 15:57:18 +0200	[thread overview]
Message-ID: <20220524135718.GA17707@cventin.lip.ens-lyon.fr> (raw)
In-Reply-To: <CACKs7VDgwmDhiUkx5MXD8KQW5KGHiDqyrL9rHo_+_AMzRQSOvg@mail.gmail.com>

On 2022-05-24 15:23:33 +0300, Stefan Puiu wrote:
> OK, now I think I understand what you mean. I guess "a following ...
> conversion" (used all over that man page, as you said) sounds a bit
> weird to me, though it might be proper English, I don't know.

It also sounds a bit weird to me (though this is grammatically
correct), but FYI, the ISO C standard uses the same words: "Specifies
that a following d, i, o, u, x, or X conversion specifier applies to
[...]", etc. So I suppose that there isn't any problem with this.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

      reply	other threads:[~2022-05-24 14:03 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
2022-05-24  7:39           ` Vincent Lefevre
2022-05-24 12:23             ` Stefan Puiu
2022-05-24 13:57               ` Vincent Lefevre [this message]

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=20220524135718.GA17707@cventin.lip.ens-lyon.fr \
    --to=vincent@vinc17.net \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=stefan.puiu@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 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.