Comment #16 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
Yeah, I am annoyed at this one. I think the right solution would be to
actually descend into the directory in question, compile there without any
directory component to the path, and get back out again afterwards.
That's probably less finicky than getting whatever pseudo-absolute
directory name quoted in a TeX-compatible manner.
--
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
