Linux Documentation
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Ian Rogers <irogers@google.com>
Cc: Alejandro Colomar <alx@kernel.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Jonathan Corbet <corbet@lwn.net>,
	dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH v3 2/4] proc_pid_fdinfo.5: Make pid clearer in the name and 1st paragraph
Date: Sat, 2 Nov 2024 05:17:20 -0500	[thread overview]
Message-ID: <20241102101720.cwp7lcidqbzkrub6@illithid> (raw)
In-Reply-To: <20241101191156.1272730-2-irogers@google.com>

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

Hi Ian,

At 2024-11-01T12:11:54-0700, Ian Rogers wrote:
> diff --git a/man/man5/proc_pid_fdinfo.5 b/man/man5/proc_pid_fdinfo.5
> index 87e6dbe56..935b54b4c 100644
> --- a/man/man5/proc_pid_fdinfo.5
> +++ b/man/man5/proc_pid_fdinfo.5
[...]
> -this is a subdirectory containing one entry for each file which the
> -process has open, named by its file descriptor.
> +this subdirectory contains one entry for each file that process
> +.IR pid
> +has open, named by its file descriptor.

`IR` is better used with two or more arguments.

As of groff 1.23 (July 2023), the man(7) package will warn you about
problem like this if you ask it to.

$ nroff -man -rCHECKSTYLE=1 /tmp/proc_pid_fdinfo_mini.5
an.tmac:/tmp/proc_pid_fdinfo_mini.5:7: style: .IR expects at least 2 arguments, got 1
proc_pid_fdinfo_mini(5)       File Formats Manual      proc_pid_fdinfo_mini(5)

Name
       /proc/pid/fdinfo - information about file descriptors

Description
       Text text text text.  One pid to rule them all and in the darkness bind
       them.

example                           2024‐11‐02           proc_pid_fdinfo_mini(5)

I think Alex has a make(1) target that assists with running groff this
way.

groff_man(7):
   Font style macros
     ... It is often necessary to set
     text in different styles without intervening space.  The macros
     .BI, .BR, .IB, .IR, .RB, and .RI, where “B”, “I”, and “R”
     indicate bold, italic, and roman, respectively, set their odd‐
     and even‐numbered arguments in alternating styles, with no space
     separating them.

One reason to pay close attention to this point is that

.IR foo bar

formats as "foobar" (with "foo" in italics), whereas

.I foo bar

formats as "foo bar", with both words in italics.

The different handling of the space is a common manifestation of error.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-02 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 19:11 [PATCH v3 1/4] proc_pid_fdinfo.5: Reduce indent for most of the page Ian Rogers
2024-11-01 19:11 ` [PATCH v3 2/4] proc_pid_fdinfo.5: Make pid clearer in the name and 1st paragraph Ian Rogers
2024-11-02 10:17   ` G. Branden Robinson [this message]
2024-12-06  6:57     ` Ian Rogers
2024-11-01 19:11 ` [PATCH v3 3/4] proc_pid_fdinfo.5: Add subsection headers for different fd types Ian Rogers
2024-11-01 19:11 ` [PATCH v3 4/4] proc_pid_fdinfo.5: Add DRM subsection Ian Rogers
2024-11-02 10:38   ` G. Branden Robinson

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=20241102101720.cwp7lcidqbzkrub6@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alx@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=irogers@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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