Please read the documentation of these flags that you
can obtain by
lilypond -dhelp
As far as I can understand, the idea is that if you use
lilypond -dlog-file foo.ly
(which is equivalent to lilypond -dlog-file=#t foo.ly )
then LilyPond should produce a file foo.log.
However, as you have noticed (even though you didn't
really use the flag correctly), no such file is produced,
so there seems to be a bug here.
/Mats
Cameron Horsburgh wrote:
When I try to compile a file foo.ly the -dlog-file switch fails. There
are two modes of failure.
$ lilypond -dlog-file=log foo.ly
compiles cleanly but no log file is produced.
If I change the name of the log file to foo.log an error is produced:
$ lilypond -dlog-file=foo.log foo.ly
GNU LilyPond 2.10.16
ERROR: Unbound variable: foo.log
I have only tested this behaviour with 2.10.16.
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
