Follow-up Comment #4, bug #67889 (group groff):
[comment #3 comment #3:]
> Aliasing the macro, that is, creating another name for a
> package's existing macro shouldn't matter.
That may be true in this instance. In the general case, the difference
between $0 and a hard-coded name could expose someone's secret identity.
.de Superman
.tm I am Superman
..
.als ClarkKent Superman
.ClarkKent
This was, as I understand it, your point about hard-coded names in diagnostic
output in bug #67815.
-mm's .LT may be the opposite situation, where @cover _should_ be set to "LT"
regardless of what alias invokes the macro. I leave that question to those
who know anything about -mm.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67889>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
