From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page proc_pid_fd.5
Date: Sun, 17 Nov 2024 10:35:47 -0600 [thread overview]
Message-ID: <20241117163547.k6cvvaz5xitbvicn@illithid> (raw)
In-Reply-To: <rkahavnoaq6iryfg26isqi7rwncw57ihenyvlzwxzt4b5qmbma@vo6iu4jdvm4d>
[-- Attachment #1: Type: text/plain, Size: 2336 bytes --]
Hi Alex,
At 2024-11-17T12:24:56+0100, Alejandro Colomar wrote:
> [CC += Branden]
What do you need from me here? I'll take a guess and review your patch.
> On Sun, Nov 17, 2024 at 10:46:22AM GMT, Helge Kreutzmann wrote:
> > Without further ado, the following was found:
> >
> > Issue: Inode -> I<inode>?
> >
> > "type:[inode]\n"
>
> I've applied the following patch:
>
> commit f3ac823f7501910031855c1f6e640f0dc5e295bb (HEAD -> contrib)
> Author: Alejandro Colomar <alx@kernel.org>
> Date: Sun Nov 17 12:23:48 2024 +0100
>
> proc_pid_fd.5: ffix
>
> Reported-by: Helge Kreutzmann <debian@helgefjell.de>
> Cc: "G. Branden Robinson" <branden@debian.org>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> diff --git a/man/man5/proc_pid_fd.5 b/man/man5/proc_pid_fd.5
> index 2e3341ad8..903063e82 100644
> --- a/man/man5/proc_pid_fd.5
> +++ b/man/man5/proc_pid_fd.5
> @@ -24,7 +24,7 @@ .SH DESCRIPTION
> .IP
> .in +4n
> .EX
> -type:[inode]
> +.IB type :[ inode ]
This markup looks okay to me, if "type" and "inode" are parameterized
and ":[" and "]" are literal.
Personally, I would use `IR` instead of `IB` since the example is of
_output_, not user input.
groff_man_style(7):
Use bold for literal portions of syntax synopses, for
command‐line options in running text, and for literals that
are major topics of the subject under discussion; for
example, this page uses bold for macro, string, and register
names. In an .EX/.EE example of interactive I/O (such as a
shell session), set only user input in bold.
But (a) the exhibit here is more an example of file content than I/O per
se, and (b) I don't recall if you have an overriding style rule for the
man-pages project.
As ever, clarity is the first principle. If the example is clear either
way, the choice of typeface for the literal parts of it is a matter of
polish, and not likely a barrier to the reader's comprehension.
> .EE
> .in
> .IP
> @@ -50,7 +50,7 @@ .SH DESCRIPTION
> .IP
> .in +4n
> .EX
> -.RI anon_inode: file-type
> +.BI anon_inode: file-type
> .EE
> .in
> .IP
>
> If anyone has comments, please let me know.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-17 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 10:46 Issue in man page proc_pid_fd.5 Helge Kreutzmann
2024-11-17 11:24 ` Alejandro Colomar
2024-11-17 16:35 ` G. Branden Robinson [this message]
2024-11-17 17:26 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 11:30 ` Alejandro Colomar
2024-11-17 11:52 ` Helge Kreutzmann
2024-11-17 11:58 ` 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=20241117163547.k6cvvaz5xitbvicn@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@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