Comment #2 on issue 2111 by [email protected]: documentation of
include-settings in Usage
http://code.google.com/p/lilypond/issues/detail?id=2111
i'd go for 3.
suggestions:
AU: Command line options for lilypond
The following options are supported:
<alphabetical list of options> (it's not sorted in version 2.15.22)
AU: 4.5 Independent includes
"Some people have written large (and useful!) code that can be shared
between projects. This code might eventually make its way into LilyPond
itself, but until that happens, you must download and \include them
manually"
<- or by using the command line options -dinclude-settings= and -I= >
(maybe a pointer to the LSR is useful here!?)
NR: 4.6.3 Style sheets
instead of using \include … every time you can also invoke lilypond with
the command line options -dinclude-settings= and -I=
and while talking about -doptions:
on the French list Nicolas Sceaux has shown an interesting possibility to
pass nearly any desired option, see
http://lilypond-french-users.1298960.n2.nabble.com/programmer-tt7102673.html#none
a new request!?
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
