Follow-up Comment #18, bug #63958 (project groff):
To re-iterate, right now, i don't see a need to change anything with respect
to the topic of this ticket.
Unless i'm unaware of some arcane corner cases, i modeled the hanging indents
in mandoc(1) to match how groff(1) does them.
Ragarding the variable-width indents in sections 1 & 8, i don't recall ever
being unhappy with them. That may be because the names of command line
commands tend to be short. Admittedly, in OpenBSD, Marc Espie blessed us with
a check-lib-depends(1) manual page, but even that still looks passable, and it
doesn't get much longer than that. The dbus-update-activation-environment(1)
manual arguably does look ugly, but such insanity is rare to the point that i
would call it irrelevant for all practical purposes.
On the other hand, long function names in section 3 are *not* unusual, so with
large variable indents, many pages in section 3 would look really bad. On top
of that, many section 3 pages document more than one function, and having a
differently wide hanging indent for every function would also be ugly. So the
currently solution of always using 4n is just fine.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63958>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
