Re: control over sectioning and splitting

[Gavin Smith]

On Sat, Dec 25, 2021 at 12:58:58PM +0100, Patrice Dumas wrote:
> On Sun, Oct 10, 2021 at 08:56:35AM -0700, Per Bothner wrote:
> > 
> > 
> > On 10/10/21 07:10, Patrice Dumas wrote:
> > > I am probably missions something, but isn't what you want obtained with
> > > --split=chapter and using sectioning commands like @section,
> > > @subsection?
> > 
> > The fundamental problem is that texinfo assumes page-splitting at a
> > particular level on the hierarchy, but that is too inflexible: It makes
> > for a non-optimal browsing expeience.
> 
> I think that @node is is a way to have more splitting (and also allow to
> have a flow that does not corresponds to the sectionning structure).
> Maybe adding nodes and setting USE_NODES could achieve what you want,
> though this could also need some testing and some modifications of the
> output.


I propose that @node could be used to used to specify splitting as you
say here, Patrice.  A @chapter or @section without a @node command would
become an officially supported and documented part of the language.

I saw somebody did this in a video recently:

https://youtu.be/KDlVGg_VgQc?t=4198

- taking out @node lines to control splitting in Info output.

@chapter or @section without @node would become a lot like
@heading except perhaps there could also be an @anchor generated
for the chapter heading as well as appearing in the table of
contents.  There would have to be a check that the name of the
automatic @anchor didn't clash with any other @node or @anchor.