At 2026-11-15T22:54:05-0600, Dave Kemper wrote: > On Sat, Nov 14, 2026 at 4:19 PM G. Branden Robinson > <[email protected]> wrote: > > +.\" Temporarily shut off style warnings on groff 1.26 and later. > > +.nr saved-warnings \n[.warn] > > +.if \n(.g&\n(.x=1&\n(.y>25 .warn -style > > This actually tests for "1.26 and later in the 1.* sequence."
Yes, and it probably would have been clearer for me to say: .if \n(.g&\n(.x=1&\n(.y>=26 .warn -style > That is, it stops working at groff 2.0 and later. Yes, but I don't regard that as a solvable problem right now because we don't have any idea what groff 2.x syntax will look like. Consider the possibility that, with AT&T parenthesis syntax now just about dead, with all System V/DWB-descended troffs that don't support GNU troff extension syntax either having a narrow focus (Plan 9) or moribund (all others), we might toss the `\n(xx` behind the `-C` compatibility mode gate. And then the foregoing would not work. I have few clear ideas for what I'd want to do with a "groff 2" syntax, but that sort of thing would be high on my list. Regards, Branden
signature.asc
Description: PGP signature
