[PATCH] doc/ctf-spec.texi: Remove "@validatemenus off"

[H.J. Lu]

On Tue, Nov 9, 2021 at 3:51 PM Nick Alcock <nick.alcock@oracle.com> wrote:
>
> On 9 Nov 2021, H. J. Lu said:
>
> > On Tue, Nov 9, 2021 at 1:29 PM Nick Alcock <nick.alcock@oracle.com> wrote:
> >> (If the latter... wonderful! If the former, I curse the world.)
> >
> > I am not a texinfo expert.  Since @validatemenus isn't used in GCC,
> > glibc nor binutils texinfo file, I assume that it isn't needed.
>
> That's a risky assumption. Those manuals are all old enough that they
> all have handwritten menus, which I was specifically trying to avoid on
> the grounds that writing Texinfo menus by hand is an odious waste of
> time and just repeats stuff given elsewhere in the document anyway. If
> you take @validatemenus out without doing anything else, in at least
> some Texinfos (up to 6.4, perhaps, from the code?), the menus in the
> generated info document are all going to vanish, leaving the nodes
> inaccessible.
>
> I'll give things a try with 6.8 tomorrow and see if the nodes actually
> are being autogenerated even without @validatemenus: there is no longer
> any documentation saying that automatic menu generation even exists, but
> there still seems to be code to do it (see commit
> c86d0ee139f7449aa72f81bc07af47684c1a6c3b and
> tp/Texinfo/Structuring.pm:complete_node_tree_with_menus().)
>
> But it looks like we'll at least need to bump the texinfo requirement
> for ctf-spec.texi generation further, until some version that generates
> menus even in the absence of @validatemenus. The total lack of menution
> of all the refactorings in this area (or even the removal of
> @validatemenus) in the NEWS makes it quite hard to tell what version
> that might be... given that this is only a specfile it's probably
> acceptable to go all the way to 6.8 (iff I find that works).
>

You can check with and without "@validatemenus off" using an older
textinfo.


-- 
H.J.