Hi Branden,
In the git HEAD of the man pages repository, I can reproduce a bug in
groff -Thtml:
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:~/
On Sun, Jun 16, 2024 at 10:10:38PM GMT, Alejandro Colomar wrote:
> Hi Branden,
>
> In the git HEAD of the man pages repository, I can reproduce a bug in
> groff -Thtml:
>
> alx@debian:~/tmp/groff$ cat keyrings.7
> .TH a s d f
> .SH foo
> .TP
> foobar
> alx@debian:~/tmp/groff$ troff -man -Thtml
Hi Doug, Branden,
On Tue, Jun 11, 2024 at 07:58:51PM GMT, Douglas McIlroy wrote:
> > I'd structure what you have like this:
> >
> > .nf
> > .EX
> > ...
> > .EE
> > .fi
>
> .EX/.EE is too dumb for this. Anything between .EE and .fi will get
> filled, which is almost certainly contrary to the purp
Hi Alex,
At 2024-06-16T23:14:56+0200, Alejandro Colomar wrote:
> Branden, how about using some register in EX/EE so that it can nest
> within nf/fi?
In your scenario I would advise the following instead:
.TH foo 1 2024-06-16 "groff test suite"
.SH Name
foo \- frobnicate a bar
.SH Description
.nf
On Sun, Jun 16, 2024 at 05:16:25PM GMT, G. Branden Robinson wrote:
> Hi Alex,
Hi Branden,
> At 2024-06-16T23:14:56+0200, Alejandro Colomar wrote:
> > Branden, how about using some register in EX/EE so that it can nest
> > within nf/fi?
>
> In your scenario I would advise the following instead:
>
On Sun, Jun 16, 2024 at 05:16:25PM GMT, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2024-06-16T23:14:56+0200, Alejandro Colomar wrote:
> > Branden, how about using some register in EX/EE so that it can nest
> > within nf/fi?
>
> In your scenario I would advise the following instead:
>
> .TH foo
