Re: [help-texinfo] producing index with texi2dvi

[Karl Berry]

Hi Graham,

    @macro funindex {WORD}
    @findex \WORD\
    @kindex \WORD\
    @end macro

I installed the following patch (\let\endinput=\empty), and now your
test file runs to completion (without makeinfo preprocessing).  Can you
get the new texinfo.tex from ftp://tug.org/tex/texinfo.tex and see if it
works on the full Lilypond?

Thanks,
Karl

*** texinfo.tex 7 May 2006 22:04:28 -0000       1.213
--- texinfo.tex 29 May 2006 00:13:06 -0000      1.214
***************
*** 3398,3401 ****
--- 3408,3437 ----
    \let\} = \myrbrace
    %
+   % I don't entirely understand this, but when an index entry is
+   % generated from a macro call, the \endinput which \scanmacro inserts
+   % causes processing to be prematurely terminated.  This is,
+   % apparently, because \indexsorttmp is fully expanded, and \endinput
+   % is an expandable command.  The redefinition below makes \endinput
+   % disappear altogether for that purpose -- although logging shows that
+   % processing continues to some further point.  On the other hand, it
+   % seems \endinput does not hurt in the printed index arg, since that
+   % is still getting written without apparent harm.
+   % 
+   % Sample source (mac-idx3.tex, reported by Graham Percival to
+   % help-texinfo, 22may06):
+   % @macro funindex {WORD}
+   % @findex xyz
+   % @end macro
+   % ...
+   % @funindex commtest
+   % 
+   % The above is not enough to reproduce the bug, but it gives the flavor.
+   % 
+   % Sample whatsit resulting:
+   % address@hidden@folio address@hidden address@hidden }}}
+   % 
+   % So:
+   \let\endinput = \empty
+   %
    % Do the redefinitions.
    \commondummies