Follow-up Comment #4, bug #65930 (group groff): [comment #3 comment #3:] > [comment #2 comment #2:] > > If I'm right about Allman not contemplating multi-line headers/footers > > His "-me Reference Manual" explicitly addressed such things when talking about the .$h (and, by reference, .$f) macro: "May be redefined to provide fancy (e.g., multi-line) headers."
Ah. I had forgotten, and didn't check.
> Intriguingly, "someone" has removed this text from the groff version of the
manual, perhaps in an attempt to hide his contemplation of such an
abomination.
<laugh> It's not so abominable from our end, nor from his I think (as we
reused his code); since the `@t` internal macro is called by the `$h` and `$f`
"API" macros, it's the redefiner's responsibility to cope with the more
troublesome vertical spacing issues that arise.
I therefore see no need to put the vanished verbiage back; the leading `$` in
the macro names imply the needful. (See the second-to-last paragraph on page
1 of _groff_'s _meref.me_.)
Or more simply:
"Go ahead and stick your fingers in, but be mindful of the teeth."
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65930>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
