[EMAIL PROTECTED] writes: > > > then used "xyzzy" as the basename for the whole process (.ly .tex .dvi > > > .eps .png etc). This patch saved my project, since python was choking on > > > the size of my source file. I had to break it into smaller pieces for > > > > lilypond-book in 2.2 will not choke on long files, if you break them > > in parts using \include. Why do you need extra features, then? > > Translation: lilypond-book still chokes on long files. The workaround is > to break them in parts using \include.
Can you provide an example of a file that chokes 2.2 lilypond-book ? > Unfortunately that workaround doesn't work for large html files. > > I would have thought the benefit of non-random filenames would be > self-evident, and I provided an example of when it was specifically > needed. I know, but I prefer to solve the underlying problem if possible. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _______________________________________________ bug-lilypond mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-lilypond
