Re: problems with user-defined command line options

[Nicolas Sceaux]

Le 23 déc. 2011 à 09:39, Marc Hohl a écrit :

> #(ly:add-option 'no-slurs #f
>      "Whether to print a slur or not.")

The "no-" prefix is dealt with specially for options.
For instance, considering an option named `foo', if you use the
command line switch:

  lilypond -dno-foo ...

then (ly:get-option 'foo) will return #f

=======foo.ly
#(ly:add-option 'foo #t "Fooing something")

#(format #t "~%foo option: ~a" (ly:get-option 'foo))
========

$ lilypond toto.ly
foo option: #t

$ lilypond -dno-foo toto.ly
foo option: #t

You may define a `slurs' option instead:
#(ly:add-option 'slurs #t "Whether to print a slur or not.")

Nicolas