But I like such constructs! I have one in every one of the 249 @section commands in the document I originally submitted with the bug report. They are there so that the Table of Contents in the PDF has a nice link from the name of the operator or function to the right place in the document (not just to the page number, which is a tiny adventitious thing off to the right from the point of view of someone who is reading the PDF document online, and then only takes you to the top of the right page). They're not really "self"-references, just references to the corresponding nodes, and until quite recently, I'm sure I was able to use them. Why would you want to forbid them? Is there a fundamental semantic problem with them, or just an implementation inconvenience?
Thanks again, dB On Mon, Nov 21, 2022 at 12:51 PM Patrice Dumas <[email protected]> wrote: > On Mon, Nov 21, 2022 at 09:12:56PM +0100, Patrice Dumas wrote: > > On Mon, Nov 21, 2022 at 07:07:05AM -0800, David Bacon wrote: > > > Wow, well done, reducing it to such a nice tidy little test case! > > > > Actually the smallest case is the following (which I thought we tested > > for...): > > > > @node sharp > > @section @ref{sharp} tuple > > The infinite recursion happens simply because the section refers to > itself. A double recursion also creates the same kind of infinite loop: > > @node n1 > @section @ref{n2} > > @node n2 > @section @ref{n1} > > What about forbidding such constructs when creating the Texinfo tree? > > -- > Pat >
