On Thu, Apr 12, 2012 at 03:45:36PM +0100, Colin Hall wrote: > On Thu, Apr 12, 2012 at 11:12:36AM +0100, James wrote: > > Hello, > > > > On 12 April 2012 01:28, Colin Hall <colingh...@gmail.com> wrote: > > > > > > On Tue, Apr 10, 2012 at 05:45:42AM -0700, Eluze wrote: > > >> > > >> I can run LilyPond with > > >> --include="D:/data/ly/includes - copy" -dinclude-settings="myInit.ly" > > >> > > >> if the init file contains a blank it doesn't work > > >> --include="D:/data/ly/includes - copy" -dinclude-settings="myInit 2.ly" > > >> > > >> I have to use 4 sets of quotes > > >> --include="D:/data/ly/includes - copy" -dinclude-settings=""""myInit > > >> 2.ly"""" > > >> > > >> this also work when the whole file with path is specified (and the path > > >> or > > >> file name contains blanks): > > >> -dinclude-settings=""""D:/data/ly/includes - copy/myInit 2.ly"""" > > >> > > >> so we have the funny situation where we can write > > >> > > >> lilypond ?-I"D:/data/ly/includes - copy" > > >> -dinclude-settings=""""D:/data/ly/includes - copy/myInit 2.ly"""" test.ly > > >> > > >> should this be documented > > > > > > No reason why not. > > > > Well yes, I'm still not even sure what the issue is here. > > > > We have already know warnings about using these '-d' commands with > > Windows which are already explicitly stated, but just to dump this as > > a 'LilyPond' issue to fix in doc is not going to help. > > > > http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-usage#basic-command-line-options-for-lilypond > > > > See the 'Note' under the --evaluate command. > > > > Is this just that? > > I'll take a look.
Good point. That works on Linux just fine. See below. prompt> prompt> prompt>lilypond -e '(define-public a 42)' -d 'include-settings="include filename with spaces.ly"' bug.ly Running Lilypond GNU LilyPond 2.15.35 Processing `bug.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `bug.ps'... Converting to `./bug.pdf'... Success: compilation successfully completed prompt> prompt> prompt> I'll try it on Windows. Cheers, Colin. -- Colin Hall _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
