Hello, On 20 August 2012 10:26, Colin Hall <colingh...@gmail.com> wrote: > On Mon, Aug 20, 2012 at 02:10:15AM -0700, Eluze wrote: >> >> Colin Hall-3 wrote >> > >> > On Mon, Aug 20, 2012 at 01:52:44AM -0700, Eluze wrote: >> >> running the command >> >> >> >> lilypond -dlog-file="my special.log" a.ly >> >> >> >> GNU LilyPond 2.15.95 >> >> <unnamed port>:1:7: While evaluating arguments to cons in expression >> >> (cons >> >> (quote log-file) (quote my) ...): >> >> <unnamed port>:1:7: Unbound variable: special.log >> >> >> >> did I use this command/option incorrectly? if not I will add this to the >> >> issue list. >> >> >> >> thanks >> >> Eluze >> > >> > On Windows? >> > >> >> exactly! Eluze > > Windows shell quoting. It's a known bug.
No, it's just a limitation of Microsoft's implementation of the 'cmd' application - which I believe is not actually a true shell. It is not specific to LilyPond - try doing any complex 'awk' commands for example and you soon have to resort to '-f [file.awk]. I have this bookmarked. http://stackoverflow.com/questions/355988/how-do-i-deal-with-quote-characters-when-using-cmd-exe It seems that opening 'cmd' with a /S and/or /C switch may make this case less painful for you. James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond