Re: error when a file with blanks is entered in -dlog-file

[Colin Hall]

On Mon, Aug 20, 2012 at 10:33:46AM +0100, James wrote:
> Hello,
> 
> On 20 August 2012 10:26, Colin Hall <address@hidden> 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.

That's true but the -d command line options in Lilypond are
particularly troublesome on both Linux and Windows, probably on MacOSX
too.

For example, the include settings option

echo "Use an include file without spaces, works fine" > /dev/null 
lilypond -d include-settings=includefilenamenospaces.ly  bug.ly

No problem there. But, introduce spaces in the filename and you get:

echo "Quoting so that the equals sign, the quotes and the spaces " > /dev/null
echo "all make it through to Lilypond" > /dev/null 
lilypond -d include-settings\=\"include\ filename\ with\ spaces.ly\" bug.ly

On Windows, for the no-spaces case:
"C:\Program Files (x86)\LilyPond-2.15.35\usr\bin\lilypond.exe" -d 
include-settings=includefilenamenospaces.ly bug.ly

On Windows, for the with-spaces case:
"C:\Program Files (x86)\LilyPond-2.15.35\usr\bin\lilypond.exe" -d 
include-settings=""""include filename with spaces.ly"""" bug.ly

I do not wish to imply that we should re-engineer the -d options, but
documenting this stuff is important, hence the tracker here:

https://code.google.com/p/lilypond/issues/detail?id=2476

Cheers,
Colin.

-- 

Colin Hall