Re: CHECKSTYLE: Report problems with a non-zero status

Hi Branden, On 2/1/22 20:34, G. Branden Robinson wrote: > That's a reasonable thing to want but it runs against the grain of how > *roff programs generally handle diagnostics and exit statuses. > > I have a recommendation or two for how you should be able to get the > behavior you want. Thanks!

Re: CHECKSTYLE: Report problems with a non-zero status

Hi Branden, On 2/1/22 20:34, G. Branden Robinson wrote: > I have a recommendation or two for how you should be able to get the > behavior you want. > > Quoting your commit diff above... > > +DEFAULT_GROFFFLAGS := -man > +DEFAULT_GROFFFLAGS += -rCHECKSTYLE=3 > +DEFAULT_GROFFFLAGS += -z > +EXTRA_G

Re: CHECKSTYLE: Report problems with a non-zero status

At 2022-01-31T00:41:09+0100, Alejandro Colomar (man-pages) wrote: > Hi Branden, > > I started using groff(1)'s -rCHECKPATCH=3 in my chessutils game suite > (consisting of exactly 1 game right now :~). See >

CHECKSTYLE: Report problems with a non-zero status

Hi Branden, I started using groff(1)'s -rCHECKPATCH=3 in my chessutils game suite (consisting of exactly 1 game right now :~). See As with C static analyzers, I added it to the