Hi Branden, On 2023-08-01 00:20, G. Branden Robinson wrote: >>> Thanks for raising this. The fix was straightforward, and you can >>> expect it in my next push to groff Git.[9] > > I may not be willing to die on this hill, but I'm willing to risk being > MEDEVACed from it. It won't matter, if everybody who really cares about > mdoc(7) is loyal to mandoc(1) unto death, which seems to approximately > be the case. > > My goal is that it not be obvious to the causal reader of a man page > whether man(7) or mdoc(7) was used to compose it. So I'm not tolerant > of gratuitous rendering differences, and in groff 1.23.0 I made changes > to both packages to align them better with each other. I'm happy if > only an expert man page author can tell without looking at the source. Function prototypes are the biggest difference, IMO. I prefer how man(7) pages show function prototypes (the type and the variable are formatted differently). Though I'll give to mdoc(7) that parentheses and commas in roman are nice. .3 pages are easily distinguished in the first screenful of text without looking at the source, in the SYNOPSIS. Cheers, Alex -- <http://www.alejandro-colomar.es/> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature