Re: control over sectioning and splitting

[Patrice Dumas]

Hello,

Resuscitating an old thread as I tried to progress on the issue.

On Fri, Jan 28, 2022 at 05:39:04PM +0100, Patrice Dumas wrote:
> On Sun, Jan 23, 2022 at 10:20:03AM -0800, Per Bothner wrote:
> > 
> > On 1/22/22 02:07, Gavin Smith wrote:
> > > @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.
> > 
> > If the @section/whatever is immediately preceded by an @anchor,
> > one can use the explicit anchor instead.  In a sense the @anchor
> > functions like the @missing node command, except in terms of splitting.
> 
> I see that indeed, there is currently no good way to associate a
> sectionning command with an anchor preceding it such that links appear
> before the heading and not after, and still be considered to be with
> this sectioning command and not the previous one.  Yet, I do not think
> that associating an @anchor to the next sectioning command is correct to
> do in every situations, as the @anchor could really be meant to be at
> the end of the preceding section.

I tried to progress on that issue, not by tweaking anchors associated to
@*heading but starting to work on nodes association with the following
@*heading command.

My idea is that using @node followed by @*heading command could possibly
solve this use case as in:


@c =============================================================
@node Frontends including browsers
@chapter Frontends including browsers

A frontend is a program that handles the user interface.

@node Copy and paste
@heading Copy and paste

Paste should work on all front-ends if domterm makes use of libclipboard.

@node Electron
@subheading Electron

Start the Electron frontend (if available) with the --electron option.

@c =============================================================

The first issue I remarked is that, with USE_NODES=1 there was both a
heading for the @node and for the @*heading command.  I just commited a
change that associate node without section to following heading command
and I made it the default.  See:
https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=c7c7b6ce369ea79870a6d4bf40d3b17d0e0757c3

There are still at least two issues for this to correspond to Per
use cas (if I understood well, feel free to correct me).

First, there are, with USE_NODES=1, navigation panels for each of the
nodes.  They are mostly empty for lone nodes without explicit
directions, but not completly empty.  Are thses navigation panels
wanted?  Should there be a specific way to remove them, or are the
existing ways ok?

Second, there is no <div> set up to include the content associated to
the @node.  Is it an issue?

-- 
Pat