public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v3] man/man2/statmount.2: Document STATMOUNT_BY_FD
Date: Thu, 5 Mar 2026 16:24:31 -0600	[thread overview]
Message-ID: <20260305222431.geycb2pof2k7sdba@illithid> (raw)
In-Reply-To: <aam6Yn6ZJhM9PQup@devuan>

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

[CC list trimmed way down since this is a *roff/formatting issue]

Hi Alex,

At 2026-03-05T18:19:30+0100, Alejandro Colomar wrote:
> BTW, Branden, I'm getting a diagnostic from groff:
> 
> 	TROFF		.tmp/man/man2/statmount.2.pdf.set
> 	! (troff -mandoc -Tpdf -wbreak -rS12 -rU0  <.tmp/man/man2/statmount.2.pdf.troff 2>&1 >.tmp/man/man2/statmount.2.pdf.set) \
> 	| grep ^ >&2
> 	.tmp/man/man2/statmount.2:155: warning: table row does not fit on page 2
> 
> But the PDF looks good to me.  Would you mind looking at that page and
> telling me what you'd do with that diagnostic, and whether I should care
> about it?

I can't reproduce this diagnostic with groff 1.23.0 or 1.24.0.

> 	.tmp/man/man2/statmount.2:155: warning: table row does not fit on page 2

This warning means that a row of the table might be vertically
encroaching into the footer margin; in extreme cases, might overprint
the page footer itself; and in really loony cases, format text beyond
the bottom of the page.

My copy of the document is this one:

	commit 7178f0e15db66a3616a900fc8a4007466633159b
	Author: Bhavik Sachdev <b.sachdev1904@gmail.com>
	Date:   Thu Feb 26 08:40:16 2026 +0530

$ ~/groff-1.24.0/bin/groff -t -ww -mandoc -Tpdf -rS12 -rU0 -z \
  man/man2/statmount.2 2>&1 | grep . || echo NO DIAGNOSTICS
NO DIAGNOSTICS
$ ~/groff-1.23.0/bin/groff -t -ww -mandoc -Tpdf -rS12 -rU0 -z \
  man/man2/statmount.2 2>&1 | grep . || echo NO DIAGNOSTICS
NO DIAGNOSTICS

As you can see, I've turned on _all_ warnings (`-ww`).

Looking at the table source:

$ sed -n '154,171p' man/man2/statmount.2
.TS
lB l.
STATMOUNT_SB_BASIC      /* Want/got sb_* */
STATMOUNT_MNT_BASIC     /* Want/got mnt_* */
STATMOUNT_PROPAGATE_FROM        /* Want/got propagate_from */
STATMOUNT_MNT_ROOT      /* Want/got mnt_root  */
STATMOUNT_MNT_POINT     /* Want/got mnt_point */
STATMOUNT_FS_TYPE       /* Want/got fs_type */
STATMOUNT_MNT_NS_ID     /* Want/got mnt_ns_id */
STATMOUNT_MNT_OPTS      /* Want/got mnt_opts */
STATMOUNT_FS_SUBTYPE    /* Want/got fs_subtype */
STATMOUNT_SB_SOURCE     /* Want/got sb_source */
STATMOUNT_OPT_ARRAY     /* Want/got opt_{num,array} */
STATMOUNT_OPT_SEC_ARRAY /* Want/got opt_sec_{num,array} */
STATMOUNT_MNT_UIDMAP    /* Want/got uidmap{_num,} */
STATMOUNT_MNT_GIDMAP    /* Want/got gidmap{_num,} */
STATMOUNT_SUPPORTED_MASK        /* Want/got supported mask flags */
.TE

...I don't see any reason why you should get that diagnostic.

1.  You're not using any text blocks.  Text blocks are formatted in a
    diversion and contain (line) breaks, so they can get "tall".

2.  You're not using any other features to make a table row "tall", for
    example by performing "local motion" with the `\v` escape sequence.
    Formatting equations in a table cell is the more traditional means
    of encountering this problem.

Can you reproduce this problem from the command line, without using your
Makefile?

Regards,
Branden

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

  reply	other threads:[~2026-03-05 22:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 14:45 [PATCH v2 00/10] man/man2/statmount.2: Document New Features Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 01/10] man/man2/statmount.2: Document req.mnt_ns_id and STATMOUNT_MNT_NS_ID Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 02/10] man/man2/statmount.2: Document STATMOUNT_MNT_OPTS Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 03/10] man/man2/statmount.2: Document STATMOUNT_FS_SUBTYPE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 04/10] man/man2/statmount.2: Document STATMOUNT_SB_SOURCE Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 05/10] man/man2/statmount.2: Document STATMOUNT_OPT_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 06/10] man/man2/statmount.2: Document STATMOUNT_OPT_SEC_ARRAY Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 07/10] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 08/10] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-22 14:45 ` [PATCH v2 09/10] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-22 14:46 ` [PATCH v2 10/10] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-22 21:52 ` [PATCH v2 00/10] man/man2/statmount.2: Document New Features Alejandro Colomar
2026-02-23 14:10   ` [PATCH v2 1/4] man/man2/statmount.2: Document STATMOUNT_{UIDMAP,GIDMAP} Bhavik Sachdev
2026-02-23 15:41     ` Alejandro Colomar
2026-02-23 18:17       ` [PATCH v2] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev
2026-02-24  0:21         ` Alejandro Colomar
2026-02-26  3:10           ` [PATCH v3] " Bhavik Sachdev
2026-03-04 14:58             ` Alejandro Colomar
2026-03-05  0:13               ` Askar Safin
2026-03-05  0:42                 ` Alejandro Colomar
2026-03-05  2:18                 ` Aleksa Sarai
2026-03-05 17:19               ` Alejandro Colomar
2026-03-05 22:24                 ` G. Branden Robinson [this message]
2026-03-05 22:45                   ` Alejandro Colomar
2026-03-05 22:55                     ` G. Branden Robinson
2026-03-06  7:51                 ` Bhavik Sachdev
2026-02-23 14:10   ` [PATCH v2 2/4] man/man2/statmount.2: Document STATMOUNT_SUPPORTED_MASK Bhavik Sachdev
2026-02-23 14:10   ` [PATCH v2 3/4] man/man2/statmount.2: Document req.mnt_ns_fd Bhavik Sachdev
2026-02-23 14:10   ` [PATCH v2 4/4] man/man2/statmount.2: Document STATMOUNT_BY_FD Bhavik Sachdev

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=20260305222431.geycb2pof2k7sdba@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox