[bug #64639] [mom] odd output with #64421 reproducer

2023-09-10 Thread G. Branden Robinson
Update of bug #64639 (project groff): Status:None => Confirmed Assigned to:None => PTPi Summary: [mom] bug #64421 is a mom-bug => [mom] odd output with #64421 reproducer

[bug #64421] [troff] link-time optimization changes `.m` register initialization

2023-09-10 Thread G. Branden Robinson
Update of bug #64421 (project groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0

[bug #64651] [bjarnigroff] wrong indent in "input.cpp"

2023-09-10 Thread G. Branden Robinson
Update of bug #64651 (project groff): Status:None => Invalid Assigned to:None => gbranden Open/Closed:Open => Closed Summary:

[bug #64651] [troff] wrong indent in "input.cpp"

2023-09-10 Thread Bjarni Ingi Gislason
URL: Summary: [troff] wrong indent in "input.cpp" Group: GNU roff Submitter: bjarniig Submitted: Sun 10 Sep 2023 01:29:58 PM UTC Category: Core Severity: 3 -

[bug #64639] [mom] odd output with #64421 reproducer

2023-09-10 Thread G. Branden Robinson
Follow-up Comment #4, bug #64639 (project groff): Aha, that makes sense. Once again my guess at how _mom_ works was all wrong. :-O I should have known, because the `COLOR` macro's definition has been stable for something like 20 years. If it was as griefed as my hypothesis had it, many people

[bug #64639] [mom] odd output with #64421 reproducer

2023-09-10 Thread Peter Schaffter
Follow-up Comment #3, bug #64639 (project groff): [comment #2 comment #2:] > The issue with the input in comment #1 appears to be that _mom_ assumes that a color named "default" exists (for me, it certainly defines a string _named_ `default` with the _contents_ `default`). cat