David Kastrup <[email protected]> writes: > Matthias Steup <[email protected]> writes: > >> Matthias Steup <matthias.steup <at> arcor.de> writes: >> >>> >>> Lilypond-book seems to be broken since lilypond version 18.0. The score runs >>> beyond the margin of the page. Up to 16.2 everything was working fine. I >>> work with MikTex and lilypond. >> >> Please consider it as a serious bug!! > > My guess is that you don't have the MikTeX executables in your PATH, so > lilypond-book is unable to find them for a test run of the page width.
Ah, I remember now. It was some TEXINPUTS manipulation with a syntax incompatible with Windows. It does not appear that the respective issue ever was entered into the tracker even though it was discussed on the list. Sigh. git log -S TEXINPUTS cranks out commit aefc5a4057a0a61f1d7e4411cc1c5061d9aea6b7 Author: Julien Rioux <[email protected]> Date: Wed Jan 23 18:21:22 2013 -0500 lilypond-book: Textwidth detection with included file (issue 3136). Fix the automatic textwidth detection performed by lilypond-book. This failed for lytex files that include an external file in the preamble, when such file was compiled in an --output directory different from the working directory, because then the included file was missing. We use TEXINPUTS to let the latex process know where to look for input files. as the culprit, version 2.17.17. -- David Kastrup _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
