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

[Colin Hall]

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. Please submit a documentation suggestion and one of
us can create a tracker for it.

> or is there a chance to make the -d option treat
> the string between one set of quotes as a file name?

I am sure it could be done but I doubt it will be done any time
soon. Besides, there are workarounds you have already identified:
- avoid filenames with spaces
- for filenames with spaces use quadruple quotes on Windows

Cheers,
Colin.

-- 

Colin Hall