Follow-up Comment #6, bug #67889 (group groff): [comment #5 comment #5:] > I'm happy to see an interesting conversation unfold regarding this > (possibly?) minor (lint) issue. What might be helpful to come to a better > understanding and decision on how to best proceed is to look at where and how > @cover is being used. A quick and possibly incomprehensive search reveals it > is only used as part of a @warning message in the definition of the @disable > macro.
I think you're right. IIRC, I put that feature in. One cover page feature
shuts off the others and diagnoses the fact if someone tries to change cover
page features mid-document. My objective, as I recall, was to tell the user
*why* they couldn't use the feature they wanted, by naming the macro they'd
already called that selected a cover page mechanism and foreclosed use of the
subsequent one.
An "incomprehensive search". I like that coinage. I'm gonna steal that.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67889>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
