Follow-up Comment #3, bug #68242 (group groff): At 2026-04-14T22:02:11-0400, Dave wrote: > Update of bug #68242 (group groff): > > Severity: 3 - Normal => 1 - Wish > > _______________________________________________________ > > Follow-up Comment #2: > > [comment #1 comment #1:] >> As long as some jackanapes doesn't innovate a warning >> category name that starts with a decimal numeral, > > I have a proposal for a category name that starts with a C0 control > character. That should be no problem, right?
You can aways try your luck with AT&T-descended troffs. ;-)
>> I wonder if Heirloom's `warn` request accepts complex
>> expressions as I envision.
>
> Not quite with the syntax you spitballed, but conceptually, it seems
> to.
>
> $ echo '.warn -missing' | htroff > /dev/null
> $ echo '.warn all-missing' | htroff > /dev/null
> troff: unknown warning category all-missing; line 1, file <standard input>
> $ echo '.warn all -missing' | htroff > /dev/null
>
> And lest one is concerned it's merely ignoring the second argument:
>
> $ echo '.warn all -hissing' | htroff > /dev/null
> troff: unknown warning category hissing; line 1, file <standard input>
Right, that's even simpler. I was thinking too rigidly about
_chmod_(1). With this approach I can use `has_arg()` to govern the
argument processing loop.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68242>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
