Follow-up Comment #7, bug #64592 (project groff):
[comment #6 comment #6:]
> See comment #3 which mentions two registers which reflect the default
value.
I apologize for being dense, but I don't see in comment #3 (or any other
comments) what registers contain the default colors. In comment #1, Branden
mentions the color _named_ "default" but also says "I don't know that we have
access via the _roff_ language to what that default is." Comment #3 mentions
two _other_ registers that are initially populated with default values (.fn
for font and .s for type size), hence my trying to clarify whether the
objection this bug is raising is (1) that .m and .M are "odd men out" in not
being populated with default values, or (2) that no other mechanism exists to
retrieve the default colors.
I make the distinction because (2) can be solved in a way that doesn't break
compatibility. (I don't know if this particular aspect of compatibility is
important to anyone. But some users might use the existing behavior, for
example to test whether any colors changes have yet been made in a document.)
But your example in the original submission might be trying to show that the
.m/.M behavior also complicates certain aspects of color handling, meaning (1)
is the root problem.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64592>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
