On Thu, Jan 23, 2020 at 07:56:24PM +0100, Patrice Dumas wrote:
> On Mon, Jan 20, 2020 at 02:12:16PM +, Gavin Smith wrote:
> > On Sun, Nov 03, 2019 at 10:17:05AM +0100, Patrice Dumas wrote:
> > > I attach an example that generates such a list right after the heading.
> > > Something that looks
On Mon, Jan 20, 2020 at 02:12:16PM +, Gavin Smith wrote:
> On Sun, Nov 03, 2019 at 10:17:05AM +0100, Patrice Dumas wrote:
> > I attach an example that generates such a list right after the heading.
> > Something that looks strange is that the node names are used in the
> > navigation header, w
On Sun, Nov 03, 2019 at 10:17:05AM +0100, Patrice Dumas wrote:
> I attach an example that generates such a list right after the heading.
> Something that looks strange is that the node names are used in the
> navigation header, while the sections names are used in the list of
> subordinate sectio
On Sun, Nov 03, 2019 at 10:17:05AM +0100, Patrice Dumas wrote:
> On Fri, Nov 01, 2019 at 02:12:37PM +, Gavin Smith wrote:
> > I would like a way of having a menu in each HTML file that lists the
> > section names of subordinate nodes. This would replace the menu that
> > already exists which
On Fri, Nov 01, 2019 at 02:12:37PM +, Gavin Smith wrote:
> I would like a way of having a menu in each HTML file that lists the
> section names of subordinate nodes. This would replace the menu that
> already exists which is generated from the @menu block in the source.
> I don't believe the
I would like a way of having a menu in each HTML file that lists the
section names of subordinate nodes. This would replace the menu that
already exists which is generated from the @menu block in the source.
I don't believe there is any way to do this currently with texi2any.
The reasons that t
