Status: Accepted Owner: ---- Labels: Type-Documentation Needs-policy
New issue 2216 by [email protected]: add the internal functions to the "Application Usage" manual
http://code.google.com/p/lilypond/issues/detail?id=2216 Eluze wrote : everybody knows how cumbersome it is to write parameters in a shell - it would be nice to have them in a lilypond file. LilyPond provides an alternative for many of the command line options but they are not well documented in an appropriate context. here is a list of the approx 50 command line options provided by LilyPond (with -dhelp or #(ly:option-usage)) with their counterparts in LilyPond. http://old.nabble.com/file/p33107771/doptions%2Bdefine%2Bdefault.csv doptions+define+default.csv most of them work as expected (I only checked about half of the items under Windows 7) with a few exceptions: show-available-fonts <---> #(ly:font-config-display-fonts) help <---> #(ly:option-usage) read-file-list (get error messages; how is it supposed to be used?) verbose <---> #(ly:set-option 'verbose #t) --> no result my suggestion is to add the internal functions to the "Application Usage" manual. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
