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

Update of bug#64592 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0

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

Update of bug#64592 (group groff): Item Group: Warning/Suspicious behaviour => Feature change Status: Need Info => In Progress ___ Follow-up Comment #14: Thanks, Peter.

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

Follow-up Comment #13, bug#64592 (group groff): [comment #12 comment #12:] > If no one objects to my proposed change in comment #10, please set this ticket's status to "Confirmed" and I'll take care of it. > > Or someone else can. It's a one-liner! But I don't know what _mom_(7) will need to

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

Follow-up Comment #12, bug#64592 (group groff): If no one objects to my proposed change in comment #10, please set this ticket's status to "Confirmed" and I'll take care of it. Or someone else can. It's a one-liner! But I don't know what _mom_(7) will need to do. Adding Peter to CC list

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

Follow-up Comment #11, bug #64592 (project groff): After the change I ran the code in comment #1 and now the second line works fine (the first line will never work properly because we don't stack colour changes). Interestingly the call to \m[\*[curcol]] where curcol contains the word "default",

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

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 +++

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

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

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

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 #64592] [troff] registers .m and .M contain no initial value

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,

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

Follow-up Comment #6, bug #64592 (project groff): [comment #5 comment #5:] > Is the problem that registers .m and .M don't behave like other registers (containing the default values), or that the roff language offers no way to retrieve these defaults? See comment #3 which mentions two registers

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

Follow-up Comment #5, bug #64592 (project groff): Is the problem that registers .m and .M don't behave like other registers (containing the default values), or that the roff language offers no way to retrieve these defaults? ___ Reply to

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

Follow-up Comment #3, bug #64592 (project groff): Hi Branden, Just a few thoughts really, I agree the registers are behaving as currently documented, the question is whether the current behaviour makes sense. Groff currently has no concept of opacity, gropdf allows pdfs included by pdfpic to

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

Follow-up Comment #2, bug #64592 (project groff): Hi Deri, Any thoughts on this issue, and my remarks in comment #1? ___ Reply to this item at: ___

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

Update of bug #64592 (project groff): Item Group: Incorrect behaviour => Warning/Suspicious behaviour Status:None => Need Info Assigned to:None => gbranden