Hi Alex,
At 2024-06-16T22:49:38+0200, Alejandro Colomar wrote:
> > alx@debian:~/tmp/groff$ cat keyrings.7
> > .TH a s d f
> > .SH foo
> > .TP
> > foobar
> > alx@debian:~/tmp/groff$ troff -man -Thtml <./keyrings.7 >/dev/null
> > free(): double free detected in tcache 2
> > Aborted
> > alx@debian:
Hi Branden,
On Mon, Jun 17, 2024 at 01:43:38PM GMT, G. Branden Robinson wrote:
> Me neither.
>
> I bisected it down to this.
>
> 0951ff53e47cfc8dda792e23f2111268bd3dd81b is the first bad commit
> commit 0951ff53e47cfc8dda792e23f2111268bd3dd81b
> Author: G. Branden Robinson
> Date: Thu Aug 10
G. Branden Robinson to Anton Shepelev:
> > This means that one must /set/ rather than unset
> > GROFF_SGR to restore the normal nroff behavior.
>
> This advice, while still applicable to groff 1.22.4, is
> becoming stale. Distributors that introduced the
> GROFF_SGR Debianism have now started to
G. Branden Robinson:
> People frequently run into trouble because they usually
> don't want the text of function prototypes filled, but the
> prototypes can also get lengthy, and they don't know how
> to make the text adapt to the available terminal width in
> the absence of filling. (Short answe
