[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-17 Thread Deri James
Follow-up Comment #8, bug #64592 (project groff): Sorry, my fault, I was not clear. My reference to the registers in comment #3 was intended to show that your statement "registers .m and .M don't behave like other registers (containing the default values)" was the problem. I'm not sure (2) can be

[bug #64892] [tbl] alloc-dealloc-mismatch with "-fsanitize=address"

2023-11-17 Thread G. Branden Robinson
Update of bug #64892 (project groff): Severity: 3 - Normal => 2 - Minor Item Group: Warning/Suspicious behaviour => Lint Status:None => Need Info ___

[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-17 Thread G. Branden Robinson
Follow-up Comment #9, bug #64592 (project groff): We could certainly change the `default_color` object to give it a non-empty name. It doesn't seem like it should be a problem; the default color already can't be redefined, so it's okay if it means different things for stroke and fill. There is a

[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-17 Thread G. Branden Robinson
Follow-up Comment #10, bug #64592 (project groff): Except for updating documentation (and mom(7)), the change I mentioned in comment #9 looks this easy. diff --git a/src/libs/libgroff/color.cpp b/src/libs/libgroff/color.cpp index 32a1bc8e7..8417c2074 100644 --- a/src/libs/libgroff/color.cpp +++