From: Jonny Grant <jg@jguk.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: argz_create
Date: Tue, 27 Oct 2020 15:03:15 +0000 [thread overview]
Message-ID: <eefb1d45-ab48-e32d-596b-43d748f192da@jguk.org> (raw)
In-Reply-To: <ede6e5d0-53af-aacb-3bdf-95ad1ffad097@gmail.com>
On 27/10/2020 13:01, Michael Kerrisk (man-pages) wrote:
> On 10/27/20 11:43 AM, Jonny Grant wrote:
>> Hello Mtk
>>
>> I noticed "nonzero" needs a hyphen "non-zero", could that be changed please?
>>
>> Also there is a word "nonempty" which isn't a word, and isn't needed I feel :-
My proposal was to remove the word "nonempty", rather than replace it.
> Please see man-pages(7).
>
https://man7.org/linux/man-pages/man7/man-pages.7.html
Yes, I can see those listed there.
Google "non-empty" 1Bn results
Google "nonempty" 6M results
However "nonempty" is not an English, or American English expression we would ever use. Even "non-empty" isn't English, we'd say "not empty", although in this sentence there is no need to have this at all.
Some are sensible, eg "pathname" is actually typically an argument name, so although it's not an English word, we know what it is. Same with "username" "timezone" etc.
Maybe in another 50 years "nonempty" will be a word, but for now it isn't, so the hyphen is needed. Same as "non-NULL"
How to go about proposing this improvement to man-pages?
Jonny
next prev parent reply other threads:[~2020-10-27 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 14:18 argz_create Jonny Grant
2020-10-26 16:08 ` argz_create Michael Kerrisk (man-pages)
2020-10-26 16:16 ` argz_create Michael Kerrisk (man-pages)
2020-10-26 21:12 ` argz_create Jonny Grant
2020-10-27 10:43 ` argz_create Jonny Grant
2020-10-27 13:01 ` argz_create Michael Kerrisk (man-pages)
2020-10-27 15:03 ` Jonny Grant [this message]
2020-10-27 15:47 ` argz_create Michael Kerrisk (man-pages)
2020-10-26 21:08 ` argz_create Jonny Grant
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=eefb1d45-ab48-e32d-596b-43d748f192da@jguk.org \
--to=jg@jguk.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox