[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: runaway recursion in makeinfo
From: |
Gavin Smith |
Subject: |
Re: runaway recursion in makeinfo |
Date: |
Mon, 21 Nov 2022 21:55:57 +0000 |
On Mon, Nov 21, 2022 at 01:42:20PM -0800, David Bacon wrote:
> 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
Cross-reference commands don't belong in section titles. What you are
saying about the Table of Contents seems like a good feature to have,
but I would much rather fix this by changing texinfo.tex to link
the section titles, rather than trying to make sense of @ref nested
inside @section. The code in texinfo.tex is somewhat tortuous but
adding this feature still seems easier than the alternative. I'll
work on this when I find the time.
- runaway recursion in makeinfo, David Bacon, 2022/11/20
- Re: runaway recursion in makeinfo, Patrice Dumas, 2022/11/21
- Re: runaway recursion in makeinfo, David Bacon, 2022/11/21
- Re: runaway recursion in makeinfo, Patrice Dumas, 2022/11/21
- Re: runaway recursion in makeinfo, David Bacon, 2022/11/21
- Re: runaway recursion in makeinfo, Patrice Dumas, 2022/11/22
- Re: runaway recursion in makeinfo, Gavin Smith, 2022/11/22