Re: include-settings and path or file name with blanks

[James]

Hello,

On 10 April 2012 13:45, -Eluze <address@hidden> 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 or is there a chance to make the -d option treat
> the string between one set of quotes as a file name?

Oh and have you tried escaping spaces? using '\'.

You should also try to run commands in such a way (either by renaming
the files) so that there are no spaces and 'dashes' etc. This doesn't
reslove your issue but helps narrow this down to one of a limitation
of Windows' syntax in cmd than something we can fix in LilyPond.

James