1 @c -*- coding: latin-1; mode: texinfo; -*-
3 @chapter Running LilyPond
5 This chapter details the technicalities of running LilyPond.
13 * Invoking lilypond-latex::
16 @node Invoking lilypond
17 @section Invoking lilypond
18 @cindex Invoking LilyPond
19 @cindex command line options
20 @cindex options, command line
24 The @code{lilypond} may be called as follows from the command line.
27 lilypond [@var{option}]@dots{} @var{file}@dots{}
31 When invoked with a filename that has no extension, the @file{.ly}
32 extension is tried first. To read input from stdin, use a
33 dash @code{-} for @var{file}.
35 When @file{filename.ly} is processed it will produce
36 @file{filename.tex} as output (or @file{filename.ps} for PostScript
37 output). If @file{filename.ly} contains more than one @code{\score}
38 block, then the rest of the scores will be output in numbered files,
39 starting with @file{filename-1.tex}. Several files can be specified;
40 they will each be processed independently. @footnote{The status of
41 GUILE is not reset after processing a @code{.ly} files, so be careful
42 not to change any system defaults from within Scheme.}
45 @section Command line options
47 The following options are supported:
51 @item -e,--evaluate=@var{expr}
52 Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
53 Multiple @code{-e} options may be given, they will be evaluated
54 sequentially. The function @code{ly:set-option} allows for access to
55 some internal variables. Use @code{-e '(ly:option-usage)'} for more
58 @item -f,--format=@var{format}
61 A comma separated list of back-end output formats to use. Choices are
62 @code{tex} (for @TeX{} output, to be processed with La@TeX{}, and
63 @code{ps} for PostScript.
65 There are other output options, but they are intended for developers.
68 @cindex output format, setting
69 @cindex PostScript output
73 Show a summary of usage.
74 @item --include, -I=@var{directory}
75 Add @var{directory} to the search path for input files.
76 @cindex file searching
78 @item -i,--init=@var{file}
79 Set init file to @var{file} (default: @file{init.ly}).
80 @item -o,--output=@var{FILE}
81 Set the default output file to @var{FILE}.
85 Generate DVI files. In this case, the @TeX{} backend should be
86 specified, i.e. @code{-f tex}.
88 Generate pictures of each page, in PNG format. This implies @code{--ps}.
90 Generate PDF. This implies @code{--ps}.
92 Generate an output file containing the titles and the first system
96 Do not trust the @code{.ly} input.
98 When LilyPond formatting is available through a web server, the
99 @code{--safe} @b{MUST} be passed. This will prevent inline Scheme
100 code from wreaking havoc, for example
105 c4^#(ly:export (ly:gulp-file "/etc/passwd"))
109 The @code{--safe} option works by evaluating in-line Scheme
110 expressions in a special safe module. This safe module is derived from
111 GUILE @file{safe-r5rs} module, but adds a number of functions of the
112 LilyPond API. These functions are listed in @file{scm/safe-lily.scm}.
114 In addition, @code{--safe} disallows @code{\include} directives and
115 disables the use of backslashes in @TeX{} strings.
117 In @code{--safe} mode, it is not possible to import LilyPond variables
120 @code{--safe} does @emph{not} detect resource overuse. It is still
121 possible to make the program hang indefinitely, for example by feeding
122 cyclic data structures into the backend. If using LilyPond
123 on a publically accessible webserver, the process should limited in both
124 allowed CPU and memory usage.
127 Show version information.
129 Be verbose: show full paths of all files read, and give timing
133 Show the warranty with which GNU LilyPond comes. (It comes with
134 @strong{NO WARRANTY}!)
137 @section Environment variables
140 For processing both the @TeX{} and the PostScript output, the
141 appropriate environment variables must be set. The following scripts
145 @item @file{buildscripts/out/lilypond-profile}
147 @item @file{buildscripts/out/lilypond-login} (for C-shells)
150 They should normally be sourced as part of the login process. If these
151 scripts are not run from the system wide login process, then you must
154 @cindex installing LilyPond
156 If you use sh, bash, or a similar shell, then add the following to
157 your @file{.profile}:
159 . @var{/the/path/to/}lilypond-profile
162 If you use csh, tcsh or a similar shell, then add the following to
163 your @file{~/.login}:
165 source @var{/the/path/to/}lilypond-login
168 Of course, in both cases, you should substitute the proper location of
171 These scripts set the following variables:
174 To make sure that @TeX{} and lilypond find data files (among
175 others @file{.tex}, @file{.mf} and @file{.tfm}),
176 you have to set @code{TEXMF} to point to the lilypond data
177 file tree. A typical setting would be
179 @{/usr/share/lilypond/1.6.0,@{!!/usr/share/texmf@}@}
187 @cindex printing postscript
189 The binary itself recognizes the following environment variables:
192 This specifies a directory where locale messages and
193 data files will be looked up by default. The directory should contain
194 subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
197 This selects the language for the warning messages.
201 @cindex LILYPONDPREFIX
204 @section Error messages
206 @cindex error messages
207 Different error messages can appear while compiling a file:
213 Something looks suspect. If you are requesting something out of the
214 ordinary then you will understand the message, and can ignore it.
215 However, warnings usually indicate that something is wrong with the
219 Something is definitely wrong. The current processing step (parsing,
220 interpreting, or formatting) will be finished, but the next step will
226 Something is definitely wrong, and LilyPond cannot continue. This
227 happens rarely. The most usual cause is misinstalled fonts.
229 @cindex trace, Scheme
233 Errors that occur while executing Scheme code are caught by the Scheme
234 interpreter. If running with the verbose option (@code{-V} or
235 @code{--verbose}) then a call trace is printed of the offending
238 @cindex Programming error
239 @item Programming error
240 There was some internal inconsistency. These error messages are
241 intended to help the programmers and debuggers. Usually, they can be
242 ignored. Sometimes, they come in such big quantities that they obscure
243 other output. In this case, file a bug-report.
245 @item Aborted (core dumped)
246 This signals a serious programming error that caused the program to
247 crash. Such errors are considered critical. If you stumble on one,
253 @cindex errors, message format
254 If warnings and errors can
255 be linked to some part of the input file, then error messages have the
259 @var{filename}:@var{lineno}:@var{columnno}: @var{message}
260 @var{offending input line}
263 A line-break is inserted in offending line to indicate the column
264 where the error was found. For example,
267 test.ly:2:19: error: not a duration: 5:
272 These locations are LilyPond's best guess about where the warning or
273 error occured, but (by their very nature) warning and errors occur
274 when something unexpected happens. If you can't see an error in the
275 indicated line of your input file, try checking one or two lines
276 above the indicated position.
280 @section Reporting bugs
283 @cindex reporting bugs
285 If you have input that results in a crash or an erroneous output, then
286 that is a bug. We try respond to bug-reports promptly, and fix them as
287 soon as possible. Help us by sending a defective input file, so we can
288 reproduce the problem. Make it small, so we can easily debug the
289 problem. Don't forget to tell which version of LilyPond you use! Send
290 the report to @email{bug-lilypond@@gnu.org}.
292 When you've found a bug, have a look at our
293 @uref{http://lilypond.org/doc/v2.3/bugs/,bug database} to see if it
294 has already been reported. You could also try doing a few searches
295 on the mailing list for the bug. Sometimes the bug will have already
296 been reported and a fix or workaround is already known.
298 Here is an example of a good bug report:
302 It seems that placement of accidentals is broken. In the
303 following example, the accidental touches the note head.
305 Using Mac OSX 10.3.5, fink package lilypond-unstable
316 \override Accidental #'extra-offset = #'(1.0 . 0)
322 @section Editor support
327 @cindex modes, editor
328 @cindex syntax coloring
329 @cindex coloring, syntax
331 There is support from different editors for LilyPond.
335 Emacs has a @file{lilypond-mode}, which provides keyword
336 autocompletion, indentation, LilyPond specific parenthesis matching
337 and syntax coloring, handy compile short-cuts and reading LilyPond
338 manuals using Info. If @file{lilypond-mode} is not installed on your
339 platform, then read the
341 @uref{../../../topdocs/out-www/INSTALL.html,installation instructions}.
344 installation instructions.
349 For @uref{http://www.vim.org,VIM}, a @file{vimrc} is supplied, along with
350 syntax coloring tools. For more information, refer to the
352 @uref{../../../topdocs/out-www/INSTALL.html,installation instructions}.
355 installation instructions.
361 The @uref{http://www.jedit.org/,jEdit} editor has a LilyPond plugin.
362 This plugin includes a DVI viewer, integrated help and viewing via
363 GhostScript. It can be installed by doing @key{Plugins > Plugin
364 Manager}, and selecting @code{LilyTool} from the @key{Install} tab.
368 All these editors can be made to jump in the input file to the source
369 of a symbol in the graphical output. See @ref{Point and click}.
374 @node Invoking lilypond-latex
375 @section Invoking lilypond-latex
377 Before LilyPond 3.0, the @code{lilypond} program only generated music
378 notation. Titles and page layout was done in a separate wrapper
379 program. For compatibility with older files, this wrapper program has
380 been retained as @code{lilypond-latex}. It uses the LilyPond program
381 and La@TeX{} to create a nicely titled piece of sheet music. Use of
382 this program is only necessary if the input file contains special
383 La@TeX{} options or formatting codes in markup texts.
385 The @code{lilypond-latex} wrapper is invoked from the command-line as
388 @code{lilypond-latex} [@var{option}]@dots{} @var{file}@dots{}
391 To have @code{lilypond-latex} read from stdin, use a dash @code{-} for
392 @var{file}. The program supports the following options.
394 @cindex stdin, reading
398 Keep the temporary directory with all output
399 files. The temporary directory is created in the current directory as @code{@code{lilypond}.dir}.
402 @item -I,--include=@var{dir}
403 Add @var{dir} to LilyPond's include path.
404 @item -o,--output=@var{file}
405 Generate output to @var{file}. The extension of @var{file} is ignored.
407 Also generate pictures of each page, in PNG format.
409 Also generate a picture of the first system of the score.
418 @item -s,--set=@var{key}=@var{val}
419 Add @var{key}= @var{val} to the settings, overriding those specified
420 in the files. Possible keys: @code{language}, @code{latexheaders},
421 @code{latexpackages}, @code{latexoptions}, @code{papersize},
422 @code{linewidth}, @code{orientation},
425 Show version information.
427 Be verbose. This prints out commands as they are executed, and more
428 information about the formatting process is printed.
430 Print even more information. This is useful when generating bug reports.
432 Show the warranty with which GNU LilyPond comes. (It comes with
433 @strong{NO WARRANTY}!)
438 @subsection Additional parameters
440 The @code{lilypond} program responds to several parameters specified
441 in a @code{\layout} section of the input file. They can be overridden
442 by supplying a @code{--set} command line option.
446 Specify La@TeX{} language: the @code{babel} package will be
447 included. Default: unset.
449 Read from the @code{\header} block.
452 Specify additional La@TeX{} headers file.
453 Normally read from the @code{\header} block. Default value: empty.
456 Specify additional La@TeX{} packages file. This works cumulative,
457 so you can add multiple packages using multiple @code{-s=latexpackages} options.
458 Normally read from the @code{\header} block. Default value:
462 Specify additional options for the La@TeX{}
463 @code{\documentclass}. You can put any valid value here. This was
464 designed to allow @code{lilypond} to produce output for double-sided
465 paper, with balanced margins and page numbers on alternating sides. To
466 achieve this specify @code{twoside}.
469 Set orientation. Choices are @code{portrait} or @code{landscape}. Is
470 read from the @code{\layout} block, if set.
473 The vertical extension of the music on the page. It is normally
474 calculated automatically, based on the paper size.
477 The music line width. It is normally read from the @code{\layout}
481 The paper size (as a name, e.g. @code{a4}). It is normally read from
482 the @code{\layout} block.
485 The font encoding, should be set identical to the @code{font-encoding}
486 property in the score.