tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Alexander Ziaee" <concussious@runbox.com>
To: "tech" <tech@mandoc.bsd.lv>
Subject: Re: [Bug] Apropos - Xr Child of Nd Rendering
Date: Sat, 14 Sep 2024 23:45:35 +0000 (UTC)	[thread overview]
Message-ID: <E1spcSN-0000PH-Hj@rmmprod06.runbox> (raw)

Hello,

On 2024-09-13 16:58 -04:00 EDT, "Alexander Ziaee" <concussious@runbox.com> wrote:
> On 2024-09-13 11:49 -04:00 EDT, "Ingo Schwarze" <schwarze@usta.de> wrote:
>> Alexander Ziaee wrote on Mon, Sep 02, 2024 at 05:01:57PM +0000:

>>> [0] https://man-dev.freebsd.org/jail.conf
>>
>> I recommend making this
>>
>>   .Sh NAME
>>   .Nm jail.conf
>>   .Nd configuration file for system jails
>>   .Sh DESCRIPTION
>>   The
>>   .Nm
>>   file consists of one or more jail definitions statements
>>   for use by the
>>   .Xr jail 8
>>   management program.
>>
>> The phrase "and parameter or variable statements within those jail
>> definitions" is misplaced in the first sentence.  Not only is the
>> first sentence supposed to be as clear and concise as possible
>> without going down any rabbit holes; this phrase also requires
>> the basic syntax of a definition statement to be established first.
>>
>> The second sentence is also quite bad: "looks something like a C
>> compound statement" is just vague.  A manual page needs to define
>> syntax and semantics with precision, not wave its hands around
>> hoping the reader might guess what the actual rules are.
>>
>> Maybe something like
>>
>>   A jail definition statement consists of a single word, the
>>   name of the jail, an opening curly brace, a list of at least
>>   (insert the minimum number here) parameter assignments,
>>   and a closing curly brace.
>>   A parameter assignment consists of a single word, the parameter
>>   name, an equal sign, a value enclosed in double quotes,
>>   and a terminating semicolon.
>>
>> For people who speak C, seeing the similarity is trivial; for
>> people who don't, mentioning it is nothing but a distraction,
>> so do not mention it.  Also, saying "similar" in a manual page
>> is very bad unless you exhaustive explain the commonalities
>> and differences - but then the text usually becomes excessively
>> verbose.
>>
>> Alternatively, the second sentence could simply be:
>>
>>   The syntax of a jail definitions statement is as follows:
>>   .Bd -unfilled
>>   .Ar jail_name Cm \&{
>>   .Bd -unfilled -offset indent -compact
>>   .Ar parameter_name Cm = Qq Ar value ;
>>   \&...
>>   .Ed
>>   .Cm \&}
>>   .Ed
>>
>> I tend to prefer a through description though, optionally
>> followed by a syntax display - but visualization of the
>> syntax can also wait for the EXAMPLES section if desired.
>>
>> The rest of the first paragraph also looks disorganized.
>> The sentence "Each jail is required to have a name at the front
>> of its definition." is a gratuitious repetition of what was
>> already said.  In general, this manual seems of low quality and
>> in dire need of a lot of basic editorial work.

Here is the PR [0] in case you are interested sir, thank you again.

[0] : https://github.com/freebsd/freebsd-src/pull/1422

Best,
Alex--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv


             reply	other threads:[~2024-09-14 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 23:45 Alexander Ziaee [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-13 20:58 Alexander Ziaee
2024-09-02 17:01 Alexander Ziaee
2024-09-13 15:49 ` Ingo Schwarze

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=E1spcSN-0000PH-Hj@rmmprod06.runbox \
    --to=concussious@runbox.com \
    --cc=tech@mandoc.bsd.lv \
    /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).