Keith OHara <[email protected]> writes: > Phil Holmes <mail <at> philholmes.net> writes: > >> >> > whenever we use <at> notation{text}, then there is a paragraph break > before >> >> > the "text". It took a while to figure out the guilty commit, but it is >> >> > 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from >> >> > upstream". >> >> > > > I think you found the correct cause, but I cannot see how it causes this > exact problem. Every macro defined in our include-files *macros.texi is > preceded by an extra line-break.
We have some changes of our own (actually reverts of stuff I have trouble believing working in any reasonable manner). The question is whether the results are different with the pristine texinfo.tex. > The pdfs on the webpage show the problem. > > The change to texinfo was requested here > http://lists.gnu.org/archive/html/bug-texinfo/2015-04/msg00037.html > and made here > http://lists.gnu.org/archive/html/texinfo-commits/2015-04/msg00030.html > but that change makes 'active' in the TeX sense a range of characters > that are non-printing in Latin1. > > If I could remember how to run texinfo on a 5-line example file, I might > send a bug-report to texinfo You start the 5-line example file with \input texinfo and follow it with the example. Then you run tex on it. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
