Re: groff: grops and grodvi crash on invalid input

2020-11-18 Thread G. Branden Robinson
Hi Brian, Following up on an almost 14 year old bug report... I can't reproduce these SEGVs with groff git HEAD. I would have thought they're the same bug since the groff output drivers outsource all of their parsing to the driver library, src/libs/libdriver/input.cpp. However, there's some sug

Re: Release Candidate 1.23.0.rc1

2020-11-18 Thread Bertrand Garrigues via
Hi Branden, Dave, On Sun, Nov 15 2020 at 01:23:17 AM, "G. Branden Robinson" wrote: > At 2020-11-14T08:01:45-0600, Dave Kemper wrote: >> I wonder if these warnings (introduced in commit 75c0873c), generated >> by "configure" on a system that doesn't have a uchardet library, >> overstate the case

Re: Release Candidate 1.23.0.rc1

2020-11-18 Thread Dave Kemper
On 11/14/20, G. Branden Robinson wrote: > At 2020-11-14T08:01:45-0600, Dave Kemper wrote: >> I wonder if these warnings (introduced in commit 75c0873c), generated >> by "configure" on a system that doesn't have a uchardet library, >> overstate the case a little: > > Maybe, but that dates back to 2

Re: Release Candidate 1.23.0.rc1

2020-11-18 Thread Dave Kemper
Hi Bertrand. I saw your reply after sending mine. On 11/18/20, Bertrand Garrigues wrote: > The 1st warning is not very visible True, although if one runs configure on an 80-column display, it's a little more visible because it's the only output line to wrap. > but it's main role is to help yo