2 @node Invoking LilyPond
3 @chapter Invoking LilyPond
5 This chapter details the technicalities of running LilyPond.
9 * Invoking lilypond:: Titling LilyPond scores.
10 * Invoking the lilypond binary::
17 @node Invoking lilypond
18 @section Invoking lilypond
20 Nicely titled output is created through a separate program:
21 @file{@code{lilypond}} is a script that uses the LilyPond formatting
22 engine (which is in a separate program) and La@TeX{} to create a
23 nicely titled piece of sheet music, in PDF (Portable Document Format)
27 @code{lilypond} [@var{option}]@dots{} @var{file}@dots{}
30 To have @code{lilypond} read from stdin, use a dash @code{-} for @var{file}.
32 The @code{lilypond} program supports the following options:
36 Keep the temporary directory with all output
37 files. The temporary directory is created in the current directory as @code{@code{lilypond}.dir}.
38 @item -d,--dependencies
39 Write @code{Makefile} dependencies for every input file.
42 @item -I,--include=@var{dir}
43 Add @var{dir} to LilyPond's include path.
45 Produce MIDI output only.
47 Do not run @file{lilypond-bin}. Useful for debugging @code{lilypond}.
48 @item -o,--output=@var{file}
49 Generate output to @var{file}. The extension of @var{file} is ignored.
51 Do not generate (PDF) or PS.
54 @cindex Scalable fonts
56 @c why is this comment here? --hwn
58 If you use lilypond-book or your own wrapper files, do not use
59 @code{\usepackage[[T1]@{fontenc@}} in the file header but do not forget
60 @code{\usepackage[latin1]@{inputenc@}} if you use any other
61 non-anglosaxian characters.
64 Also generate pictures of each page, in PNG format.
66 Gzip the postscript file.
68 Make a .HTML file with links to all output files.
70 Also generate a picture of the first system of the score.
79 @item -s,--set=@var{key}=@var{val}
80 Add @var{key}= @var{val} to the settings, overriding those specified
81 in the files. Possible keys: @code{language}, @code{latexheaders},
82 @code{latexpackages}, @code{latexoptions}, @code{papersize},
83 @code{pagenumber}, @code{linewidth}, @code{orientation},
86 Show version information.
88 Be verbose. This prints out commands as they are executed, and more
89 information about the formatting process is printed.
91 Print even more information. This is useful when generating bugreports.
93 Show the warranty with which GNU LilyPond comes. (It comes with
94 @strong{NO WARRANTY}!)
97 @subsection Titling layout
99 @code{lilypond} extracts the following header fields from the LY files
100 to generate titling; an example demonstrating all these fields is in
101 @inputfileref{input/test,lilypond-testpage.ly}:
105 The title of the music. Centered on top of the first page.
107 Subtitle, centered below the title.
109 Name of the poet, left flushed below the subtitle.
111 Name of the composer, right flushed below the subtitle.
113 Meter string, left flushed below the poet.
115 Name of the opus, right flushed below the composer.
117 Name of the arranger, right flushed below the opus.
119 Name of the instrument, centered below the arranger.
121 To whom the piece is dedicated.
123 Name of the piece, left flushed below the instrument.
125 A text to print in the header of all pages. It is not called
126 @code{header}, because @code{\header} is a reserved word in LilyPond.
128 A text to print in the footer of the first page. Default is to
129 print the standard footer also on the first page. Note that if the
130 score is only page, the first page is also the last page and in this
131 case, the tagline is printed instead of the copyright.
133 A text to print in the footer of all but the last page.
135 Line to print at the bottom of last page. The default text is ``Engraved by LilyPond @var{version-number}''.
146 @subsection Additional parameters
148 The @code{lilypond} program responds to several parameters specified
149 in a @code{\paper} section of the input file. They can be overridden
150 by supplying a @code{--set} command line option.
154 Specify La@TeX{} language: the @code{babel} package will be
155 included. Default: unset.
157 Read from the @code{\header} block.
160 Specify additional La@TeX{} headers file.
162 Normally read from the @code{\header} block. Default value: empty.
165 Specify additional La@TeX{} packages file. This works cumulative,
166 so you can add multiple packages using multiple @code{-s=latexpackages} options.
167 Normally read from the @code{\header} block. Default value:
171 Specify additional options for the La@TeX{}
172 @code{\documentclass}. You can put any valid value here. This was
173 designed to allow @code{lilypond} to produce output for double-sided
174 paper, with balanced margins and pagenumbers on alternating sides. To
175 achieve this specify @code{twoside}.
178 Set orientation. Choices are @code{portrait} or @code{landscape}. Is
179 read from the @code{\paper} block, if set.
182 The vertical extension of the music on the page. It is normally
183 calculated automatically, based on the paper size.
186 The music line width. It is normally read from the @code{\paper}
190 The paper size (as a name, e.g. @code{a4}). It is normally read from
191 the @code{\paper} block.
194 If set to @code{no}, no page numbers will be printed. If set to a
195 positive integer, start with this value as the first page number.
199 The font encoding, should be set identical to the @code{font-encoding}
200 property in the score.
205 @node Invoking the lilypond binary
206 @section Invoking the lilypond binary
207 @cindex Invoking LilyPond
208 @cindex command line options
209 @cindex options, command line
213 The LilyPond system consists of two parts: a binary executable, which
214 is responsible for the formatting functionality, and support scripts,
215 which post-process the resulting output. Normally, the support scripts
216 are called, which in turn invoke the @code{lilypond-bin}
217 binary. However, @code{lilypond-bin} may be called directly as
221 lilypond-bin [@var{option}]@dots{} @var{file}@dots{}
225 When invoked with a filename that has no extension, the @file{.ly}
226 extension is tried first. To read input from stdin, use a
227 dash @code{-} for @var{file}.
229 When @file{filename.ly} is processed it will produce
230 @file{filename.tex} as output (or @file{filename.ps} for PostScript
231 output). If @file{filename.ly} contains more than one @code{\score}
232 block, then the rest of the scores will be output in numbered files,
233 starting with @file{filename-1.tex}. Several files can be specified;
234 they will each be processed independently. @footnote{The status of
235 GUILE is not reset across invocations, so be careful not to change any
236 system defaults from within Scheme.}
239 @section Command line options
241 The following options are supported:
245 @item -e,--evaluate=@var{expr}
246 Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
247 Multiple @code{-e} options may be given, they will be evaluated
248 sequentially. The function @code{ly:set-option} allows for access to
249 some internal variables. Use @code{-e '(ly:option-usage')} for more
252 @item -f,--format=@var{format}
255 Output format for sheet music. Choices are @code{tex} (for @TeX{}
256 output, to be processed with plain @TeX{}, or through @code{lilypond}),
257 @code{pdftex} for PDF@TeX{} input, @code{ps} (for PostScript),
258 @code{scm} (for a Scheme dump), @code{sk} (for Sketch) and @code{as}
261 @strong{This option is only for developers}. Only the @TeX{} output of
262 these is usable for real work.
265 @cindex output format, setting
266 @cindex Sketch output
267 @cindex ASCII-art output
268 @cindex PDFTeX output
269 @cindex PostScript output
273 Show a summary of usage.
274 @item --include, -I=@var{directory}
275 Add @var{directory} to the search path for input files.
276 @cindex file searching
278 @item -i,--init=@var{file}
279 Set init file to @var{file} (default: @file{init.ly}).
282 Disable @TeX{} output. If you have a @code{\midi} definition MIDI output
284 @item -M,--dependencies
285 Output rules to be included in Makefile.
286 @item -o,--output=@var{FILE}
287 Set the default output file to @var{FILE}.
291 Disallow untrusted @code{\include} directives, in-line
292 Scheme evaluation, backslashes in @TeX{}, code.
294 @strong{WARNING}: the @code{--safe} option has not been reviewed for a
295 long time. Do not rely on it for automatic invocation (e.g. over the
296 web). Volunteers are welcome to do a new audit.
300 Show version information.
302 Be verbose: show full paths of all files read, and give timing
306 Show the warranty with which GNU LilyPond comes. (It comes with
307 @strong{NO WARRANTY}!)
310 @section Environment variables
313 For processing both the @TeX{} and the PostScript output, the
314 appropriate environment variables must be set. The following scripts
318 @item @file{buildscripts/out/lilypond-profile}
320 @item @file{buildscripts/out/lilypond-login} (for C-shells)
323 They should normally be sourced as part of the login process. If these
324 scripts are not run from the system wide login process, then you must
327 @cindex installing LilyPond
329 If you use sh, bash, or a similar shell, then add the following to
330 your @file{.profile}:
332 . @var{/the/path/to/}lilypond-profile
335 If you use csh, tcsh or a similar shell, then add the following to
336 your @file{~/.login}:
338 source @var{/the/path/to/}lilypond-login
341 Of course, in both cases, you should substitute the proper location of
344 These scripts set the following variables:
347 To make sure that @TeX{} and lilypond find data files (among
348 others @file{.tex}, @file{.mf} and @file{.tfm}),
349 you have to set @code{TEXMF} to point to the lilypond data
350 file tree. A typical setting would be
352 @{/usr/share/lilypond/1.6.0,@{!!/usr/share/texmf@}@}
357 For processing PostScript output (obtained with
358 @code{-f ps}) with Ghostscript you have to set @code{GS_LIB} to
359 point to the directory containing library PS files.
362 For processing PostScript output (obtained with
363 @code{-f ps}) with Ghostscript you have to set @code{GS_FONTPATH} to
364 point to the directory containing PFA files.
366 When you print direct PS output, remember to send the PFA files to the
376 @cindex printing postscript
378 The binary itself recognizes the following environment variables:
381 This specifies a directory where locale messages and
382 data files will be looked up by default. The directory should contain
383 subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
386 This selects the language for the warning messages.
390 @cindex LILYPONDPREFIX
393 @section Error messages
395 @cindex error messages
396 Different error messages can appear while compiling a file:
402 Something looks suspect. If you are requesting something out of the
403 ordinary then you will understand the message, and can ignore it.
404 However, warnings usually indicate that something is wrong with the
408 Something is definitely wrong. The current processing step (parsing,
409 interpreting, or formatting) will be finished, but the next step will
415 Something is definitely wrong, and LilyPond cannot continue. This
416 happens rarely. The most usual cause is misinstalled fonts.
421 Errors that occur while executing Scheme code are caught by the Scheme
422 interpreter. If running with the verbose option (@code{-V} or
423 @code{--verbose}) then a call trace is printed of the offending
426 @cindex Programming error
427 @item Programming error
428 There was some internal inconsistency. These error messages are
429 intended to help the programmers and debuggers. Usually, they can be
430 ignored. Sometimes, they come in such big quantities that they obscure
431 other output. In this case, a bug-report should be filed.
435 @cindex errors, message format
436 If warnings and errors can
437 be linked to some part of the input file, then error messages have the
441 @var{filename}:@var{lineno}:@var{columnno}: @var{message}
442 @var{offending input line}
445 A line-break is inserted in offending line to indicate the column
446 where the error was found. For example,
449 test.ly:2:19: error: not a duration: 5:
456 @section Reporting bugs
459 @cindex reporting bugs
461 If you have input that results in a crash or an erroneous output, then
462 that is a bug. We try respond to bug-reports promptly, and fix them as
463 soon as possible. For this, we need to reproduce and isolate the
464 problem. Help us by sending a defective input file, so we can
465 reproduce the problem. Make it small, so we can easily debug the
466 problem. Don't forget to tell which version you use, and on which
467 platform you run it. Send the report to
468 @email{bug-lilypond@@gnu.org}.
471 @section Editor support
476 @cindex modes, editor
477 @cindex syntax coloring
478 @cindex coloring, syntax
480 There is support from different editors for LilyPond.
482 Emacs has a @file{lilypond-mode}, which provides keyword
483 autocompletion, indentation, LilyPond specific parenthesis matching
484 and syntax coloring, handy compile short-cuts and reading LilyPond
485 manuals using Info. If lilypond-mode is not installed on your
486 platform, then refer to the installation instructions for more
489 For @uref{http://www.vim.org,VIM}, a vimrc is supplied, along with
490 syntax coloring tools. For more information, refer to the
492 @uref{../../../topdocs/out-www/INSTALL.html,installation instructions}.
496 installation instructions.
499 For both editors, there is also a facility to jump in the input file
500 to the source of errors in the graphical output. See @ref{Point and
503 There exists a plugin for @uref{http://www.jedit.org/,jEdit}. Refer to
504 the @uref{http://lily4jedit.sourceforget.net,plugin website} for more
508 @node Point and click
509 @section Point and click
510 @cindex poind and click
512 Point and click lets you find notes in the input by clicking on them in
513 the Xdvi window. This makes it easier to find input that causes some
514 error in the sheet music.
516 To use it, you need the following software:
518 @item a dvi viewer that supports src specials:
520 @item Xdvi, version 22.36 or newer. Available from
521 @uref{ftp://ftp.math.berkeley.edu/pub/Software/TeX/xdvi.tar.gz,ftp.math.berkeley.edu}.
523 Most @TeX{} distributions ship with xdvik, which is always a few
524 versions behind the official Xdvi. To find out which Xdvi you are
525 running, try @code{xdvi -version} or @code{xdvi.bin -version}.
526 @item KDVI. A dvi viewer for KDE. You need KDVI from KDE 3.0 or
527 newer. Enable option @emph{Inverse search} in the menu @emph{Settings}.
529 Apparently, KDVI does not process PostScript specials correctly. Beams
530 and slurs will not be visible in KDVI.
539 @item an editor with a client/server interface (or a lightweight GUI
545 @item Emacs. Emacs is an extensible text-editor. It is available from
546 @uref{http://www.gnu.org/software/emacs/}. You need version 21 to use
549 @c move this elsewhere?
554 @cindex lilypond-mode for Emacs
555 @cindex syntax coloring
557 @item XEmacs. XEmacs is very similar to Emacs.
561 @item NEdit. NEdit runs under Windows, and Unix.
562 It is available from @uref{http://www.nedit.org}.
566 @item GVim. GVim is a GUI variant of VIM, the popular VI
567 clone. It is available from @uref{http://www.vim.org}.
576 Xdvi must be configured to find the @TeX{} fonts and music
577 fonts. Refer to the Xdvi documentation for more information.
579 To use point-and-click, add one of these lines to the top of your .ly
582 #(ly:set-point-and-click 'line)
584 @cindex line-location
586 When viewing, Control-Mousebutton 1 will take you to the originating
587 spot in the @file{.ly} file. Control-Mousebutton 2 will show all
590 If you correct large files with point-and-click, be sure to start
591 correcting at the end of the file. When you start at the top, and
592 insert one line, all following locations will be off by a line.
595 For using point-and-click with Emacs, add the following
596 In your Emacs startup file (usually @file{~/.emacs}):
601 Make sure that the environment variable @var{XEDITOR} is set to
603 emacsclient --no-wait +%l %f
605 @cindex @var{XEDITOR}
606 If you use XEmacs instead of Emacs, you use @code{(gnuserve-start)} in
607 your @file{.emacs}, and set @code{XEDITOR} to @code{gnuclient -q +%l %f}.
609 For using Vim, set @code{XEDITOR} to @code{gvim --remote +%l %f}, or
610 use this argument with Xdvi's @code{-editor} option.
613 For using NEdit, set @code{XEDITOR} to @code{nc -noask +%l %f}, or
614 use this argument with Xdvi's @code{-editor} option.
616 If can also make your editor jump to the exact location of the note
617 you clicked. This is only supported on Emacs and VIM. Users of Emacs version
618 20 must apply the patch @file{emacsclient.patch}. Users of version 21
619 must apply @file{server.el.patch} (version 21.2 and earlier). At the
620 top of the @code{ly} file, replace the @code{set-point-and-click} line
621 with the following line:
623 #(ly:set-point-and-click 'line-column)
625 @cindex line-colomn-location
626 and set @code{XEDITOR} to @code{emacsclient --no-wait +%l:%c %f}. Vim
627 users can set @var{XEDITOR} to @code{gvim --remote +:%l:norm%c| %f}.
633 When you convert the @TeX{} file to PostScript using @code{dvips}, it
634 will complain about not finding @code{src:X:Y} files. These complaints
635 are harmless, and can be ignored.