Proposal section numbering messed up

[Matthew Pickering]

It seems if you move all the metainfo to above the title then it
renders correctly.

Should be easy enough to fix if someone feels strongly about how these
are rendered.

Matt

On Mon, Apr 15, 2019 at 5:45 PM Matthew Pickering
<matthewtpickering at gmail.com> wrote:
>
> The ..sectnum is necessary so that when you render all the proposals
> together then the numbering is coherent.
>
> What happens if you move the ..sectnum to above the title?
>
> On that note, I think there should be a site where you can view the
> rendered proposals rather than having to do so via github preview.
>
> Cheers,
>
> Matt
>
>
> On Mon, Apr 15, 2019 at 4:08 PM Ben Gamari <ben at smart-cactus.org> wrote:
> >
> > Simon Peyton Jones via ghc-devs <ghc-devs at haskell.org> writes:
> >
> > > Why does this proposal
> > > https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0036-kind-signatures.rst
> > > start with Section 36?  (It is proposal 36.)
> > > Lots of other proposals do this too.
> >
> > That's a great question. The header contains
> >
> >     .. sectnum::
> >       :start: 36
> >
> > which mpickering added in [1]. mpickering, what was the motivation for
> > this?
> >
> > Cheers,
> >
> > - Ben
> >
> > [1] https://github.com/ghc-proposals/ghc-proposals/commit/5c2fa009a369df39cf60ebda84debbf6e5b5490d#diff-f272dc8b5fdcaf6b06c33f7e52a815aa
> > _______________________________________________
> > ghc-devs mailing list
> > ghc-devs at haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs