Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

[lilypond]

Comment #3 on issue 2139 by address@hidden: Doc AU: command line options  
- where to use equal signs in short and long term definitions
http://code.google.com/p/lilypond/issues/detail?id=2139

I'm confused - I've never used -d= before, I always used -d…

but in fact

-dgui works as well as -d=gui=#t but -d=gui does not!

and
-d=include-settings="C:/data/ly/includes/myInit2.ly" doesn't work!

so it seems that you need the equal sign when going for the  
--define-default variant and -d=var=val works if you have the whole  
assignment after the equal sign but not with the implicit assignment of the  
truth value?!

I would be happy with a definition like you describe (after clarifying the  
1st equal sign) , e.g.

[-d | --define-default] [=]var[=val] (if that's not too confusing)

maybe adding

[ly:set-option 'var 'val)

and *not* listing all the options as you propose. it would be enough to  
list the options which are not consistent.

there is another category of command line options which obviously can not  
be invoked as an internal function (e.g. -dgui): they should be listed as  
exceptions to the general rule we are trying to establish:

  #(ly:set-option 'log-file "loglog" )
  #(ly:set-option 'include-settings "G:/data/ly/includes/myInit2.ly")
  #(ly:set-option 'gui #t)
  #(ly:set-option 'verbose #t )
  …

any comments/corrections by a builder/developer?