Simon Tatham <[email protected]> wrote:
> With mancfg.but on the command line too, the headings are discarded,
> because mancfg.but contains the Halibut directive \cfg{man-mindepth}{2},
> and the \U headings are at depth 1.
[...]
> This works for the PuTTY man pages because their internal sections are
> defined using the \H directive, which means a second-level heading
> within a chapter.
Correction: I got all my depths wrong in this text. \U is depth 0, not
depth 1. Each PuTTY man page has a \H (level 1) heading reading "Man
page for foo", and the internal NAME, SYNOPSIS etc are \S (level 2), so
that the whole lot can be collected under a single level-0 appendix
heading.
I'll update man-ipbt.but to have the same structure, so that it can be
built with the same doc/CMakeLists.txt.
> But probably a better permanent fix from a "minimal downstream diff"
> perspective is to change the heading level in man-ipbt.but so that the
> same build command _will_ work the same way between the two projects.
> I'll probably do that fix upstream when I get a chance.
Clarification: "upstream" vs "downstream" got a bit confused here. I
mean this should be done (and I will do it) in _my_ ipbt repository,
i.e. upstream from Debian's POV, but downstream from my POV in the sense
that ipbt is a downstream of PuTTY.
Cheers,
Simon
--
import hashlib; print((lambda p,q,g,y,r,s,m: (lambda w:(pow(g,int(hashlib.sha1(
m.encode('ascii')).hexdigest(),16)*w%q,p)*pow(y,r*w%q,p)%p)%q)(pow(s,q-2,q))==r
and s%q!=0 and m)(12342649995480866419, 2278082317364501, 1670428356600652640,
5398151833726432125, 645223105888478, 1916678356240619, "<[email protected]>"))
