From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] printf.3: ffix
Date: Sat, 22 Oct 2022 23:37:09 +0200 [thread overview]
Message-ID: <c50e6f4b-cfc9-a814-7fd9-5e80cb6885dd@gmail.com> (raw)
In-Reply-To: <20221021184106.7689-1-jwilk@jwilk.net>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
Hi Jakub,
On 10/21/22 20:41, Jakub Wilk wrote:
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
> ---
> man3/printf.3 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man3/printf.3 b/man3/printf.3
> index 8f944190b..85b5b4173 100644
> --- a/man3/printf.3
> +++ b/man3/printf.3
> @@ -193,8 +193,8 @@ and
> below) and each conversion specifier asks for the next
> argument (and it is an error if insufficiently many arguments are given).
> One can also specify explicitly which argument is taken,
> -at each place where an argument is required, by writing "%m$" instead
> -of \(aq%\(aq and "*m$" instead of \(aq*\(aq,
> +at each place where an argument is required, by writing "%\fIm\fP$" instead
I've always had doubts about how those things should be formatted. Could you
please explain why you'd format it that way?
Thanks,
Alex
> +of \(aq%\(aq and "*\fIm\fP$" instead of \(aq*\(aq,
> where the decimal integer \fIm\fP denotes
> the position in the argument list of the desired argument, indexed starting
> from 1.
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-22 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 18:41 [PATCH] printf.3: ffix Jakub Wilk
2022-10-22 21:37 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 9:00 Jakub Wilk
2020-03-26 7:49 ` Michael Kerrisk (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=c50e6f4b-cfc9-a814-7fd9-5e80cb6885dd@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
/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 NNTP newsgroup(s).