From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: srcfix
Date: Tue, 29 Sep 2020 14:13:26 +0200 [thread overview]
Message-ID: <9b8303fe-969e-c9f0-e3cd-0590b342d5bf@gmail.com> (raw)
In-Reply-To: <20200928132959.x4koforqnzohxh5u@jwilk.net>
On 9/28/20 3:29 PM, Jakub Wilk wrote:
> Hi Branden!
>
> In groff_man_style(7) you wrote:
>> Unused macro arguments are more often simply omitted, or good style
>> suggests that a more appropriate macro be chosen, that earlier
>> arguments are more important than later ones, or that arguments have
>> identical significance such that skipping any is superfluous.
>
> After 15 minutes of gawking at this sentence, I still don't understand
> what are you trying to say here. The sentence should be either
> thoroughly rephrased or removed.
I must say that I too found it hard to parse. I presume, Branden,
that you mean:
[[
Unused macro arguments are more often simply omitted, or good style
suggests
EITHER (1)
that a more appropriate macro be chosen,
(2)
that earlier arguments are more important than later ones, or
(3)
that arguments have
identical significance such that skipping any is superfluous.
]]
But it takes a few scans to work that out. Perhaps break
this into smaller pieces, or add some explicit structuring
elements to the sentence?
Thanks,
Michael
--
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:[~2020-09-29 12:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:03 [PATCH 1/2] system_data_types.7: srcfix Alejandro Colomar
2020-09-25 8:03 ` [PATCH 2/2] " Alejandro Colomar
2020-09-25 10:40 ` Michael Kerrisk (man-pages)
2020-09-25 11:28 ` [PATCH v2 " Alejandro Colomar
2020-09-25 12:02 ` Michael Kerrisk (man-pages)
2020-09-25 12:46 ` Alejandro Colomar
2020-09-25 10:39 ` [PATCH 1/2] " Michael Kerrisk (man-pages)
2020-09-27 6:10 ` G. Branden Robinson
2020-09-27 20:24 ` Alejandro Colomar
2020-09-28 12:58 ` G. Branden Robinson
2020-09-28 13:29 ` Jakub Wilk
2020-09-28 13:40 ` G. Branden Robinson
2020-09-29 12:13 ` Michael Kerrisk (man-pages) [this message]
2020-09-30 10:12 ` G. Branden Robinson
2022-08-19 18:03 ` Jakub Wilk
2022-08-19 23:53 ` Alejandro Colomar
2022-08-20 5:43 ` G. Branden Robinson
2022-08-20 11:57 ` .TH 4th field (Was: [PATCH 1/2] system_data_types.7: srcfix) Alejandro Colomar
2022-08-20 12:20 ` G. Branden Robinson
2022-08-20 12:40 ` Alejandro Colomar
2022-08-20 13:04 ` Alejandro Colomar
2022-08-21 11:46 ` Alejandro Colomar
2022-08-24 13:22 ` Ingo Schwarze
2022-08-24 15:04 ` Alejandro Colomar
2022-08-24 17:12 ` Ingo Schwarze
2022-08-24 19:37 ` Alejandro Colomar
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=9b8303fe-969e-c9f0-e3cd-0590b342d5bf@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=g.branden.robinson@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 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.