"Phil Holmes" <m...@philholmes.net> writes: >> > proposed version. Edit bin/book_latex.py , adding the lines with
>> File "C:\Program Files\LilyPond\usr\bin\lilypond-book.py", line 362, in >> find_toplevel_snippets >> snip = klass (type, m, formatter, line_number, global_options) >> File "out/book_snippets.py", line 815, in __init__ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This would suggest that we are not talking about bin/book_latex.py but rather about something like out/book_latex.ly regarding which version is found from the search path. >> I'm no expert on how -book calculates >> line width. > > Then I'm confused as to why you had me update bin/book_latex.py at > all. The output above is exactly the same as what I originally > reported: > http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00452.html Yes, and it very much does not look like your change affected any file that is actually getting used by Python. Since I don't have a Windows system, my own directory structure is different here. It's probably worth mentioning that the followup errors here don't exactly seem like the most user friendly thing either. > Because other developers are. I was talking you through how it might > be possible for you to provide a testing point for one of them. Well, it would appear that we should aim to put out 2.19.3 next weekend. It will contain the fix and then we can hopefully get feedback on the actual installation rather than a botched attempt of patching the correct file. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
