1 @node Invoking LilyPond
3 @chapter Invoking LilyPond
4 @cindex Invoking LilyPond
5 @cindex command line options
6 @cindex options, command line
11 lilypond [OPTION]... [FILE]...
14 @unnumberedsec Options
18 @item -e,--evaluate=@var{code}
19 Evaluates the Scheme @var{code} before parsing @file{.ly}
20 files. Multiple @code{-e} options may be given. They will be evaluated
23 @item -f,--format=@var{format}
24 Output format for sheet music. Choices are tex (for @TeX{}
25 output), ps (for PostScript), scm (for a Scheme
26 dump), and as (for ASCIIScript).
30 For processing both the @TeX{} and the PostScript output, you must
31 have appropriate environment variables set. For @TeX{}, you have to
32 set @code{MFINPUTS} and @code{TEXINPUTS} to point to the directory
33 containing LilyPond metafont and .tex files. For processing the
34 PostScript with Ghostscript, you have to set @code{GS_FONTPATH} to
35 point to the directory containing LilyPond @file{pfa} files.
37 Scripts to do this are included in
38 @file{buildscripts/out/lilypond-profile} (for sh shells) and
39 @file{buildscripts/out/lilypond-login} (for C-shells), and should
40 normally be run as part of your login process.
44 Show a summary of usage.
45 @item --include, -I=DIRECTORY
46 Add @file{DIRECTORY} to the search path for input files.
47 @cindex file searching
50 Set init file to @file{FILE} (default: @file{init.ly}).
53 Disable @TeX{} output. If you have a @code{\midi} definition, it will do the
55 @item -M,--dependencies
56 Output rules to be included in Makefile.
57 @item -o,--output=FILE
58 Set the default output file to @file{FILE}.
60 Disallow untrusted @code{\include} directives, in-line
61 Scheme evaluation, backslashes in @TeX{}, code.
63 @strong{WARNING}: the @code{--safe} option has not been reviewed for a
64 long time; do not rely on it for automatic invocation (e.g. over the
65 web). Volunteers are welcome to do a new audit.
68 Show version information
72 Show the warranty with which GNU LilyPond comes. (It comes with
73 @strong{NO WARRANTY}!)
77 When invoked with a filename that has no extension, LilyPond will try
78 adding `@file{.ly}' as an extension first.
80 When LilyPond processes @file{filename.ly} it will produce
81 @file{filename.tex} as output (or @file{filename.ps} for PostScript
82 output). If @file{filename.ly} contains more than one @code{\score}
83 block, then LilyPond will output the rest in numbered files, starting
84 with @file{filename-1.tex}. Several files can be specified; they will
85 each be processed independently. @footnote{The status of GUILE is not
86 reset across invocations, so be careful not to change any default
87 settings from within Scheme .}
89 @section Environment variables
93 additional directories for finding lilypond data. The
94 format is like the format of @file{PATH}.
96 This specifies a directory where locale messages and
97 data files will be looked up by default. The directory should contain
98 subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
101 selects the language for the warning messages of LilyPond.