On Tue, Feb 18, 2025 at 05:28:22PM +0100, pertu...@free.fr wrote:
> > Then if we used @xrefname instead, then it would make sense that this
> > should also provide the text for links to both the node and the anchor:
> >
> > @node Document Permissions
> > @nodedescription Ensuring your manual is free.
> > @anchor{Software Copying Permissions}@c old node name
> > @xrefname Document Permissions
> >
> > Such @anchors, in between a @node and a sectioning command (or heading
> > command, or @xrefname) could possibly be treated as a special case.
>
> I think that it is too much special casing that would lead to unexpected
> results and too much code to handle, since we could have instead a
> simpler alternative, with a command like
> @anchornamed{Software Copying Permissions, Document Permissions}@c old node
> name
>
I am going to implement a command in texinfo.tex called @namedanchor
that works like this as I think it is clear now that we agree that
it would be a good idea.
