[bug #66700] [me] .2c macro with one argument gives unexpected warning

Follow-up Comment #12, bug #66700 (group groff): [comment #3 comment #3:] > Attaching proposed patch. I confirm this silences the warning and doesn't regress anything in the limited parts of -me that I exercise. ___ Reply to this item at:

[bug #66707] some versions of pnmcrop produce spurious warnings

URL: Summary: some versions of pnmcrop produce spurious warnings Group: GNU roff Submitter: barx Submitted: Fri 24 Jan 2025 12:45:41 PM CST Category: General S

[bug #61302] [tests] non-portable use of echo

Follow-up Comment #12, bug #61302 (group groff): [comment #11 comment #11:] > I'll open a new ticket for this Bug #66707. ___ Reply to this item at: __

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #7, bug #66675 (group groff): At 2025-01-24T20:31:06-0500, Dave wrote: > Follow-up Comment #6, bug #66675 (group groff): > The problem is worse than originally reported as well, Not happy to hear it, but glad you caught it. Some status and commentary: 1. I've made progress on

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #6, bug #66675 (group groff): The problem is worse than originally reported as well, and has nothing to do with .char and its ilk. $ echo 'Foo\[u202Z]bar' | groff -a troff: :1: warning: can't find special character 'u202Z' Foobar That's expected. However, you can edit your fo