[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Providing extra information for Info menu generation
From: |
Patrice Dumas |
Subject: |
Re: Providing extra information for Info menu generation |
Date: |
Tue, 14 Feb 2023 23:04:09 +0100 |
On Tue, Feb 14, 2023 at 07:24:57PM +0000, Gavin Smith wrote:
> For example, in the main menu in the bash manual:
>
> * Job Control:: What job control is and how Bash allows you
> to use it.
>
> In the Texinfo source, this node could be defined like
>
> @node Job Control
> @nodeelaboration What job control is and how Bash allows you to use it.
Seems a very good idea to me. Much more semantic. To keep the same
vocabulary it could be @nodedescription.
I wonder if we should also allow using a block command if the
description is too long to fit on a line.
We would also need something similar for @dircategory.
> We could take this idea a bit further and allow arbitrary
> cross-references from nodes that would appear in Info menus, as
> a kind of "see also" link for the node. This would enable the
> generation of non-hierarchical manuals as a collection of nodes.
> (This may not be as useful, though.)
I haven't fully understood, but it looks like something that is in
the Mallard format too to allow for something more like a collection of
nodes.
--
Pat