Re: using quotes in command-line-commands under Windows

[Eluze]

David Kastrup <dak <at> gnu.org> writes:

> 
> Eluze <eluzew <at> gmail.com> writes:
> 
> > in
> > http://lilypond.org/doc/v2.15/Documentation/usage/command_002dline-
usage#Command-line-options-for-lilypond
> > there are examples using single quotes:
> >
> > lilypond -e '(define-public a 42)'
> > -dpoint-and-click='#f'
> >
> > this does not work under windows where you have to use double quotes!
> >
> >
> > i suggest to add a general information in or after the following line
> >
> > The following options are supported:
> > [under Windows - where quotes are needed - double-quotes must be used!]
> 
> I might be mistaken, but doesn't Windows even require the quotes to be
> around _all_ of an argument, so -dpoint-and-click="#f" would not work,
> but "-dpoint-and-click=#f" would?
> 
> It is also conceivable that this depends on the startup stub of whatever
> compiler you happened to be using.
> 
> I know why I don't do Windows.
> 
anything works:

-dpoint-and-click=#f
-dpoint-and-click="#f"
-d"point-and-click=#f"
-"dpoint-and-click=#f"
"-dpoint-and-click=#f"

who's gonna tell us why?