Comment #11 on issue 3874 by [email protected]: Patch: lilypond-book: Fix
TEXINPUTS environment manipulation on W32
http://code.google.com/p/lilypond/issues/detail?id=3874
Ok, since I don't want two months before we have a working lilypond-book in
2.18, and since "it does not work at all" can't actually get much worse, I
tend to commit this to master right after it passing Patchy (which actually
does not test it as far as can discern).
I checked the workaround on GNU/Linux by hardwiring the test for the
workaround code, and this appeared to work as intended.
The input_dir feature appears unsupported so far in formats other than
LaTeX, so I did not mess with it in other backends. We first want to get
this behavior right for LaTeX and Windows.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
