Follow-up Comment #3, bug #67889 (group groff):
At 2026-01-06T13:06:34-0500, Dave wrote:
> Follow-up Comment #2, bug #67889 (group groff):
>
> [comment #1 comment #1:]
>> This is a source code syntax/style issue.
>
> That was my first thought. My second was that it could affect the
> output if an -mm document renames or aliases the LT macro (lesson from
> bug #67815 learned!).
If a document renames or redefines a macro, the user has moved
themselves into self-support territory. I don't think any macro package
tolerates that.
Aliasing the macro, that is, creating another name for a package's
existing macro shouldn't matter.
Example:
.P
This is my
.I mm
document.
.als Lefftenant LT
> My third thought was that I don't know how -mm uses @cover, so I don't
> actually know whether that's true.
It's an internal string that identifies which of several cover page
schemes the document uses.
groff_mm(7):
groff mm offers three frameworks for document organization. COVER/
COVEND is a flexible means of preparing any document requiring a
cover page. LT/LO aids preparation of typical Anglophone
correspondence (business letters, for example). The MT memorandum
type mechanism implements a group of formal styles historically
used by AT&T Bell Laboratories. Your document can select at most
one of these approaches; when used, each disables the others.
I guess technically, there are four schemes, which Alexis's comment #0
presents succinctly; the fourth is "none of the above", which neverless
does not foreclose the ability to use the `TL` macro to define a
document's title. But once `TL` has been seen, the cover page die has
been cast.
And, hmm, it appears that `MT` and `COVER` are interface macros that
don't dump their arguments at high debugging levels. For shame!
> At that point I'd have had to stop thinking and start investigating,
> so instead I took the easier path of turning on the telly.
Apes can't *always* brain.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67889>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
