[PATCH 12/42] find.1: improve table formatting

"G. Branden Robinson" <[email protected]> Tue, 18 Nov 2025 21:45:49 -0600
Newsgroups gmane.comp.gnu.findutils.bugs
Message-ID <20251119034549.lnqpp5gr7rlyyhuu@illithid>
* Use paragraphing macros to put vertical space above and below the
  tables (where not already present) so that they looks more like
  typographical "displays".[1]
* Simplify "XY" table definition (see groff's tbl(1) man page).  This
  simpler definition has the same result (and is more adaptable in the
  event the text of the table is revised).
* Put horizontal rule below column headings in table that uses them.
* Use thin space escape sequences `\|` between the dots of an ellipsis;
  the effect is visible only on typesetting devices.[2]  I left the
  dummy character escape sequence `\&` trailing it intact, but observe
  for the edification of nit-pickers that it has no effect in this
  context.[3]

[1] man(7) implementations are historically inconsistent with respect to
    whether a `TS` macro call should put any vertical space on the
    output, and compositional practices on the part of man page authors
    have thus been, to quote Ingo Schwarze, "wildly inconsistent".

    https://savannah.gnu.org/bugs/?62841

[2] groff_man_style(7):

       Examples of ellipsis usage are shown above, in subsection
       “Synopsis macros”.  The idiomatic roff ellipsis is three dots
       (periods) with thin space escape sequences \| internally
       separating them.

[3] tbl(1):

     Ordinarily, a table entry is typeset rigidly.  It is not filled,
     broken, hyphenated, adjusted, or populated with supplemental inter‐
     sentence space.
---
 find/find.1 | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/find/find.1 b/find/find.1
index cada7798..b9c06804 100644
--- a/find/find.1
+++ b/find/find.1
@@ -940,18 +940,16 @@ .SS "TESTS"
 .BR equal .
 The letters \fIX\fR and \fIY\fR can be any of the following letters:
 .
+.IP
 .TS
-ll
-ll
-ll
-ll
-llw(2i).
+LL.
 a	The access time of the file \fIreference\fR
 B	The birth time of the file \fIreference\fR
 c	The inode status change time of \fIreference\fR
 m	The modification time of the file \fIreference\fR
 t	\fIreference\fR is interpreted directly as a time
 .TE
+.IP
 .
 Some combinations are invalid; for example, it is invalid for
 .I X
-- 
2.30.2
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmkdPW0ACgkQ0Z6cfXEm
bc50DxAAmNEINW4Fn0UP7FEqXFRjw/wdO5evZVAXF4R1rfN4eJQBCQyG2SBny1hK
Jt9dxfC87Lsox/OG0LMu4yrwTA5BYmWdAPEL5j4qKxGUk12/T2ybabLYF6LNqrQC
xSZSf/j4EnyWUIFd4ty2jLpcM7cPi0BgmTsUN+hzpt0n24HcQ572YGL+Qrd9IFer
edGH/cAQ9NhyMjt+6bNHtdWH4AIlzUiFhVI7AjRU4wPczxyLc0GhRKKdjP2mh2/i
gOe13VWNXxK3UIeg2lA8I1CFjz2RxXYRh3cH5TlVUxTesOTmnzOdqL4keF1wxceU
LJ/Xeuk4T122DVwEINQ7HBSFKomEn1p8Si7z5zwJA+IznDhCuoq3upxpYC1MLUij
t1NECIxZTKC13AZ8iENFpgD3HPCxL9YJAvmTHWaJcVhr8+xBuYTJkt9c71+SqeZx
kbLFH3kxa066NXfCQXuXMbfy9j/KFf9T1LBQ/1vQMHBNqRyaz/WaLexeNtDPl9Zq
pZ4BJJyzyaDBi53EN8H8528FSPUXCD5Lyf/k+RqEa2nZWqixZO2kdfTJvTAc5sBd
s4ibWyCKy/LSBkP6ojPSN70tpcXHsv87nz+AzBcU2QMExQ0Q/WTrFsCu1p8vynOY
DOGF5PMEypk8rN0TuvvRyOJ2MQzd5v9GEe5R9M1VW0JJXUiO7Rc=
=8We0
-----END PGP SIGNATURE-----