Re: Inconsistent macro notation in manual pages.

"G. Branden Robinson" <[email protected]>
Newsgroups gmane.comp.printing.groff.general
Message-ID <20260221202841.qlzhm26lpyrrxuwp@illithid>
[another self-follow-up]

At 2026-02-21T13:01:02-0600, G. Branden Robinson wrote:
>     The availability of groff, which included from early days not just
>     a reimplementation of man(7) but of its SunOS 4 variant, widely
>     considered by Berkeley acolytes to be the best realization of the
>     BSD system.  (And just LOOK at how much money Bill Joy was
>     making!)

I managed to not properly construct the first sentence.  I'll recast.

Much of mdoc(7)'s reason for being was immediately undercut by the
availability of groff, which included from early days not just a
reimplementation of man(7) but of its SunOS 4 variant, widely considered
by Berkeley acolytes to be the best realization of the BSD system.  (And
just LOOK at how much money Bill Joy was making!)

Incidentally, this is why mdoc(7) partisans carry on at high volume and
great length about its superiority to man(7)--because it has "semantic"
macros.  That's the only advantage it's retained since Net/2 in 1991.

Unfortunately (or not), it has many such macros, which lengthens the
learning process and discourages adoption.

Documentation writers too often seem to adopt an attitude of
indifference to semantic markup, which might explain man(7)'s persistent
popularity, mdoc(7)'s relative lack of it, and the silence that has
faced my proposals to extend the man(7) package--backwards-compatibly,
even!--to embrace them.

https://lists.gnu.org/archive/html/groff/2023-10/msg00034.html

No matter what the environs, a horse that isn't thirsty won't drink.

The wide popularity of non-semantic markup languages like Markdown and
reStructured Text hints at a darker possibility: a lot of implementors
suck at documenting their systems with semantic tools because thinking
carefully about the semantics of their systems freezes them up.

Regards,
Branden
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEh3PWHWjjDgcrENwa0Z6cfXEmbc4FAmmaFXIACgkQ0Z6cfXEm
bc6ySA/+MnkYE9CS89DdzeLahhurQovC7B+aG64jUYH26penVeTtENntLA6jjQDs
oxENkLv/vZb3Lz0eE2ziRZzle4xgmrQIXQArjUoIvwU1W3gJSPPMaaC2SanuGez0
1Z2sdbj5mQ94mZ3w8Kl7HZPstuYqckReNcfNP6m8u9rxEFKlIfvWO92DiGWMO/kj
6r96W8H9FFNiN9Y0nRbXenFQjgSWQmIAXcbrkQ68neF8Yr6SdE8YY42Xjy689Hx5
SgC6NDApOr5/KDBzfrPjHtwM+byIPd7Zc0F2T7LJ9SMNDxXe2MFDefQc5xhkgdRT
veXGcYLT6rBSJLYwuyqwAlu/yJbPqi2asBoLpka1kKw1uE7TjOxVUSE4VlvjRknQ
Op/sacygQ2XisRocUHnI3v2LWxVekRehzn2h0WcticN0FcnV53etjF1jm3VPftvh
il8zIeU2dR0uc90d1HRpQrWxZLo3o3fXT77SWgndTTIkbi7ilX723qSZVLHfn1Xw
vzddr9y9j+Oaf7a/TI4dK3CfRnW5mzBMKfBLyt2N8iZzSeytGvFOSfacIb5ORZ0z
RImFwnhxLdM1KpiIDVT+k9k7YgXhlxAKRWgNYPBVscvLy6+ayPLc79hK7zgXPgGi
tbesEh5Qs82li7dVZJ7LY0UpjLljCGu5Adtj8FoW7HMgQ+yBtDU=
=Azyt
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.