1 @c -*- coding: utf-8; mode: texinfo; -*-
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes..
14 @node Running lilypond
15 @chapter Running @command{lilypond}
17 This chapter details the technicalities of running LilyPond.
21 * Command-line usage::
30 Most users run LilyPond through a GUI; if you have not done so
31 already, please read the @rlearning{Tutorial}. If you use an alternate
32 editor to write lilypond files, see the documentation for that
36 @node Command-line usage
37 @section Command-line usage
39 This section contains extra information about using LilyPond on the
40 command-line. This may be desirable to pass extra options to the
41 program. In addition, there are certain extra @q{helper} programs (such
42 as @code{midi2ly}) which are only available on the command-line.
44 By @q{command-line}, we mean the command line in the operating system.
45 Windows users might be more familiar with the terms @q{DOS shell} or
46 @q{command shell}. MacOS@tie{}X users might be more familiar with the terms
47 @q{terminal} or @q{console}. Some additional setup is required
48 for MacOS@tie{}X users; please see @rweb{MacOS X}.
50 Describing how to use this part of an operating system is outside the
51 scope of this manual; please consult other documentation on this topic
52 if you are unfamiliar with the command-line.
56 * Basic command line options for LilyPond::
57 * Advanced command line options for LilyPond::
58 * Environment variables::
59 * LilyPond in chroot jail::
62 @node Invoking lilypond
63 @unnumberedsubsec Invoking @command{lilypond}
65 The @command{lilypond} executable may be called as follows from
69 lilypond [@var{option}]@dots{} @var{file}@dots{}
73 When invoked with a filename that has no extension, the @file{.ly}
74 extension is tried first. To read input from stdin, use a
75 dash (@code{-}) for @var{file}.
77 When @file{filename.ly} is processed it will produce @file{filename.ps}
78 and @file{filename.pdf} as output. Several files can be specified;
79 they will each be processed independently. @footnote{The status of
80 GUILE is not reset after processing a @code{.ly} file, so be careful
81 not to change any system defaults from within Scheme.}
83 If @file{filename.ly} contains more than one @code{\book}
84 block, then the rest of the scores will be output in numbered files,
85 starting with @file{filename-1.pdf}. In addition, the value of
86 @code{output-suffix} will be inserted between the basename and the
87 number. An input file containing
90 #(define output-suffix "violin")
92 #(define output-suffix "cello")
97 will output @var{base}@file{-violin.pdf} and
98 @var{base}@file{-cello-1.pdf}.
101 @unnumberedsubsubsec Standard shell commands
103 If your shell (i.e. command window) supports normal redirects,
104 then you might find it useful to use the following commands to
105 redirect console output to a file:
110 @code{lilypond file.ly 1>stdout.log} to redirect normal output
113 @code{lilypond file.ly 2>stderr.log} to redirect error messages
116 @code{lilypond file.ly &>all.log} to redirect all output
120 Consult the documentation for your shell to see if it supports these
121 options, or if the syntax is different. Note that these are shell
122 commands and have nothing to do with lilypond.
125 @node Basic command line options for LilyPond
126 @unnumberedsubsec Basic command line options for LilyPond
128 @cindex Invoking @command{lilypond}
129 @cindex command line options for @command{lilypond}
130 @cindex options, command line
133 The following options are supported:
137 @item -d,--define-default=@var{var}=@var{val}
138 See @ref{Advanced command line options for LilyPond}.
140 @cindex Scheme, expression evaluation
141 @cindex expression evaluation, Scheme
143 @item -e,--evaluate=@var{expr}
144 Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
145 Multiple @option{-e} options may be given, they will be evaluated
148 The expression will be evaluated in the @code{guile-user} module, so
149 if you want to use definitions in @var{expr}, use
152 lilypond -e '(define-public a 42)'
156 on the command-line, and include
159 #(use-modules (guile-user))
163 at the top of the @code{.ly} file.
165 @warning{Windows users must use double quotes instead of single quotes.}
167 @cindex output, format
168 @cindex format, output
170 @item -f,--format=@var{format}
171 which formats should be written. Choices for @code{format} are
172 @code{ps}, @code{pdf}, and @code{png}.
174 Example: @code{lilypond -fpng @var{filename}.ly}
177 Show a summary of usage.
179 @item -H,--header=@var{FIELD}
180 Dump a header field to file @file{BASENAME.@var{FIELD}}.
182 @item -i,--init=@var{file}
183 Set init file to @var{file} (default: @file{init.ly}).
185 @cindex file searching
188 @item -I, --include=@var{directory}
189 Add @var{directory} to the search path for input files.
191 Multiple -I options may be given. The search will start in the first
192 defined directory, and if the file to be included is not found the
193 search will continue in subsequent directories.
195 @cindex chroot jail, running inside
197 @item -j,--jail=@var{user},@var{group},@var{jail},@var{dir}
198 Run @command{lilypond} in a chroot jail.
200 The @option{--jail} option provides a more flexible alternative to
201 @option{-dsafe}, when LilyPond formatting is being provided via a web
202 server, or whenever LilyPond executes commands sent by external sources
203 (see @ref{Advanced command line options for LilyPond}).
205 It works by changing the root of @command{lilypond} to @var{jail} just
206 before starting the actual compilation process. The user and group are
207 then changed to match those provided, and the current directory is
208 changed to @var{dir}. This setup guarantees that it is not possible (at
209 least in theory) to escape from the jail. Note that for @option{--jail}
210 to work, @command{lilypond} must be run as root, which is usually
211 accomplished in a safe way using @command{sudo}.
213 Setting up a jail can be a relatively complex matter, as we must be sure
214 that LilyPond is able to find whatever it needs to compile the source
215 @emph{inside} the jail itself. A typical chroot jail will comprise the
220 @item Setting up a separate filesystem
221 A separate filesystem should be created for LilyPond, so that it can be
222 mounted with safe options such as @code{noexec}, @code{nodev}, and
223 @code{nosuid}. In this way, it is impossible to run executables or to
224 write directly to a device from LilyPond. If you do not want to create a
225 separate partition, just create a file of reasonable size and use it to
226 mount a loop device. A separate filesystem also guarantees that LilyPond
227 cannot write more space than it is allowed.
229 @item Setting up a separate user
230 A separate user and group (say, @code{lily}/@code{lily}) with low
231 privileges should be used to run LilyPond inside the jail. There should
232 be a single directory writable by this user, which should be passed in
235 @item Preparing the jail
236 LilyPond needs to read a number of files while running. All these files
237 are to be copied into the jail, under the same path they appear in the
238 real root filesystem. The entire content of the LilyPond installation
239 (e.g., @file{/usr/share/lilypond}) should be copied.
241 If problems arise, the simplest way to trace them down is to run
242 LilyPond using @command{strace}, which will allow you to determine which
245 @item Running LilyPond
246 In a jail mounted with @code{noexec} it is impossible to execute any
247 external program. Therefore LilyPond must be run with a backend that
248 does not require any such program. As we have already mentioned, it
249 must be run with superuser privileges (which, of course, it will lose
250 immediately), possibly using @command{sudo}. It is also good practice
251 to limit the number of seconds of CPU time LilyPond can use (e.g., using
252 @command{ulimit@tie{}-t}), and, if your operating system supports it,
253 the amount of memory that can be allocated. Also see
254 @ref{LilyPond in chroot jail}.
258 @cindex output, verbosity
260 @item -l,--loglevel=@var{LEVEL}
261 Set the verbosity of the console output to @var{LEVEL}. Possible values
267 No output at all, not even error messages.
270 Only error messages, no warnings or progress messages.
273 Warnings and error messages, no progress.
276 Basic progress messages (success), warnings and errors.
279 All progress messages, warnings and errors.
282 Progress messages, warnings, errors and further execution information.
285 All possible messages, including verbose debug output.
289 @cindex directory, redirect output
290 @cindex output, setting filename
291 @cindex output, directory
293 @item -o,--output=@var{FILE} or @var{FOLDER}
294 Set the default output file to @var{FILE} or, if a folder with that name
295 exists, direct the output to @var{FOLDER}, taking the file name from the
296 input file. The appropriate suffix will be added (e.g. @code{.pdf} for
299 @cindex PS (Postscript), output
300 @cindex Postscript (PS), output
301 @cindex output, PS (Postscript)
306 @cindex PNG (Portable Network Graphics), output
307 @cindex output, PNG (Portable Network Graphics)
310 Generate pictures of each page, in PNG format. This implies
311 @option{--ps}. The resolution in DPI of the image may be set with
316 @cindex PDF (Portable Document Format), output
317 @cindex output, PDF (Portable Document Format)
320 Generate PDF. This implies @option{--ps}.
323 Show version information.
326 Be verbose: show full paths of all files read, and give timing
330 Show the warranty with which GNU LilyPond comes. (It comes with
331 @strong{NO WARRANTY}!)
336 @node Advanced command line options for LilyPond
337 @unnumberedsubsec Advanced command line options for LilyPond
341 @item -d@var{[option-name]}=@var{[value]},--define-default=@var{[option-name]}=@var{[value]}
342 This sets the equivalent internal Scheme function to @var{value}.
348 If a @var{value} is not supplied, then the default value is used. The
349 prefix @code{no-} may be added to @var{option-name} to switch @q{off} an
352 @cindex point and click, command line
365 @noindent The following are supported along with their respective
368 @multitable @columnfractions .33 .16 .51
369 @item @strong{Symbol}
371 @tab @strong{Explanation/Options}
373 @item @code{anti-alias-factor}
375 @tab Render at higher resolution (using given factor) and scale down
376 result to prevent @q{jaggies} in @code{PNG} images.
378 @item @code{aux-files}
380 @tab Create @code{.tex}, @code{.texi}, @code{.count} files in the
385 @tab Select backend. Postscript files (default) include @code{TTF},
386 @code{Type1} and @code{OTF} fonts. No subsetting of these fonts is
387 done. Using @q{oriental} character sets can lead to very large files.
391 @tab Encapsulated PostScript. This dumps every page (system) as a
392 separate @file{EPS} file, without fonts, and as one collated @file{EPS}
393 file with all pages (systems) including fonts. Used as default by
394 @command{lilypond-book}.
398 @tab Do not output a printed score; has the same effect as
399 @code{-dno-print-pages}.
403 @tab Scalable Vector Graphics. This creates a single @code{SVG} file,
404 without embedded fonts, for every page of output. It is recommended to
405 install the Century Schoolbook fonts, included with your LilyPond
406 installation, for optimal rendering. Under UNIX, simply copy these
407 fonts from the LilyPond directory (typically
408 @file{/usr/share/lilypond/VERSION/fonts/otf/}) to @file{~/.fonts/}. The
409 @code{SVG} output should be compatible with any SVG editor or user
410 agent. There is also an option @code{svg-woff} (below) for use of woff
411 font files in the SVG backend.
415 @tab Dump of the raw, internal Scheme-based drawing commands.
417 @item @code{check-internal-types}
419 @tab Check every property assignment for types.
421 @item @code{clip-systems}
423 @tab Generate cut-out snippets of a score.
427 @tab Prefix for data files (read-only).
429 @item @code{debug-gc}
431 @tab Dump memory debugging statistics.
433 @item @code{debug-gc-assert-parsed-dead}
435 @tab For memory debugging: Ensure that all references to parsed objects
436 are dead. This is an internal option, and is switched on automatically
437 for @code{`-ddebug-gc'}.
439 @item @code{debug-lexer}
441 @tab Debug the flex lexer.
443 @item @code{debug-page-breaking-scoring}
445 @tab Dump scores for many different page breaking configurations.
447 @item @code{debug-parser}
449 @tab Debug the bison parser.
451 @item @code{debug-property-callbacks}
453 @tab Debug cyclic callback chains.
455 @item @code{debug-skylines}
459 @item @code{delete-intermediate-files}
461 @tab Delete the unusable, intermediate @code{.ps} files created during
464 @item @code{dump-cpu-profile}
466 @tab Dump timing information (system-dependent).
468 @item @code{dump-profile}
470 @tab Dump memory and time information for each file.
472 @item @code{dump-signatures}
474 @tab Dump output signatures of each system. Used for regression testing.
476 @item @code{eps-box-padding}
478 @tab Pad left edge of the output EPS bounding box by the given amount
481 @item @code{gs-load-fonts}
483 @tab Load fonts via Ghostscript.
485 @item @code{gs-load-lily-fonts}
487 @tab Load only the LilyPond fonts via Ghostscript.
491 @tab Runs silently and redirect all output to a log file.
495 @strong{Note to Windows users:} By default @code{lilypond.exe} outputs
496 all progress information to the command window,
497 @code{lilypond-windows.exe} does not and returns a prompt, with no
498 progress information, immediately at the command line. The
499 @option{-dgui} option can be used in this case to redirect output to a
502 @multitable @columnfractions .33 .16 .51
507 @item @code{include-book-title-preview}
509 @tab Include book titles in preview images.
511 @item @code{include-eps-fonts}
513 @tab Include fonts in separate-system EPS files.
515 @item @code{include-settings}
517 @tab Include file for global settings, this is included before the score
520 @item @code{job-count}
522 @tab Process in parallel, using the given number of jobs.
524 @item @code{log-file}
525 @tab @code{#f [file]}
526 @tab If string @code{FOO} is given as a second argument,
527 redirect output to the log file @code{FOO.log}.
529 @item @code{max-markup-depth}
531 @tab Maximum depth for the markup tree. If a markup has more levels,
532 assume it will not terminate on its own, print a warning and return a
535 @item @code{midi-extension}
537 @tab Set the default file extension for MIDI output file to given
540 @item @code{music-strings-to-paths}
542 @tab Convert text strings to paths when glyphs belong to a music font.
544 @item @code{paper-size}
546 @tab Set default paper size. Note the string must be enclosed in
547 escaped double quotes.
549 @item @code{pixmap-format}
551 @tab Set GhostScript's output format for pixel images.
553 @item @code{point-and-click}
555 @tab Add @q{point & click} links to @code{PDF} output. See
556 @ref{Point and click}.
560 @tab Create preview images in addition to normal output.
564 This option is supported by all backends; @code{pdf}, @code{png},
565 @code{ps}, @code{eps} and @code{svg}, but not @code{scm}. It generates
566 an output file, in the form @code{myFile.preview.extension}, containing
567 the titles and the first system of music. If @code{\book} or
568 @code{\bookpart} blocks are used, the titles of @code{\book},
569 @code{\bookpart} or @code{\score} will appear in the output, including
570 the first system of every @code{\score} block if the @code{\paper}
571 variable @code{print-all-headers} is set to @code{#t}.
573 To suppress the usual output, use the @option{-dprint-pages} or
574 @option{-dno-print-pages} options according to your requirements.
576 @multitable @columnfractions .33 .16 .51
577 @item @code{print-pages}
579 @tab Generate full pages, the default. @option{-dno-print-pages} is
580 useful in combination with @option{-dpreview}.
582 @item @code{profile-property-accesses}
584 @tab Keep statistics of @code{get_property()} function calls.
586 @item @code{protected-scheme-parsing}
588 @tab Continue when errors in inline scheme are caught in the parser. If
589 set to @code{#f}, halt on errors and print a stack trace.
591 @item @code{read-file-list}
592 @tab @code{#f [file]}
593 @tab Specify name of a file which contains a list of input files to be
596 @item @code{relative-includes}
598 @tab When processing an @code{\include} command, look for the included
599 file relative to the current file (instead of the root file).
601 @item @code{resolution}
603 @tab Set resolution for generating @code{PNG} pixmaps to given value (in
608 @tab Do not trust the @code{.ly} input.
612 When LilyPond formatting is available through a web server, either the
613 @option{--safe} or the @option{--jail} option @b{MUST} be passed. The
614 @option{--safe} option will prevent inline Scheme code from wreaking
621 c4^$(ly:gulp-file "/etc/passwd")
626 The @option{-dsafe} option works by evaluating in-line Scheme
627 expressions in a special safe module. This is derived from GUILE
628 @file{safe-r5rs} module, but also adds a number of functions of the
629 LilyPond API which are listed in @file{scm/safe-lily.scm}.
631 In addition, safe mode disallows @code{\include} directives and
632 disables the use of backslashes in @TeX{} strings. It is also not
633 possible to import LilyPond variables into Scheme while in safe mode.
635 @option{-dsafe} does @emph{not} detect resource overuse, so it is still
636 possible to make the program hang indefinitely, for example by feeding
637 cyclic data structures into the backend. Therefore, if using LilyPond
638 on a publicly accessible webserver, the process should be limited in
639 both CPU and memory usage.
641 Safe mode will prevent many useful LilyPond snippets from being
644 The @option{--jail} is an even more secure alternative, but requires
645 more work to set up. See @ref{Basic command line options for LilyPond}.
647 @multitable @columnfractions .33 .16 .51
648 @item @code{separate-log-files}
650 @tab For input files @code{FILE1.ly}, @code{FILE2.ly}, etc. output log
651 data to files @code{FILE1.log}, @code{FILE2.log}, ...
653 @item @code{show-available-fonts}
655 @tab List available font names.
657 @item @code{strict-infinity-checking}
659 @tab Force a crash on encountering @code{Inf} and @code{NaN} floating
662 @item @code{strip-output-dir}
664 @tab Don't use directories from input files while constructing output
667 @item @code{svg-woff}
669 @tab Use woff font files in SVG backend.
671 @item @code{trace-memory-frequency}
673 @tab Record Scheme cell usage this many times per second. Dump the
674 results to @code{FILE.stacks} and @code{FILE.graph}.
676 @item @code{trace-scheme-coverage}
678 @tab Record coverage of Scheme files in @code{FILE.cov}.
682 @tab Verbose output, i.e. loglevel at DEBUG (read-only).
684 @item @code{warning-as-error}
686 @tab Change all warning and @q{programming error} messages into errors.
690 @node Environment variables
691 @unnumberedsubsec Environment variables
694 @cindex LILYPOND_DATADIR
696 @command{lilypond} recognizes the following environment variables:
698 @item LILYPOND_DATADIR
699 This specifies a directory where locale messages and
700 data files will be looked up by default. The directory should contain
701 subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
704 This selects the language for the warning messages.
706 @item LILYPOND_LOGLEVEL
707 The default loglevel. If LilyPond is called without an explicit loglevel
708 (i.e. no @option{--loglevel} command line option), this value is used.
710 @item LILYPOND_GC_YIELD
711 A variable, as a percentage, that tunes memory management
712 behavior. A higher values means the program uses more memory, a
713 smaller value means more CPU time is used. The default value is
719 @node LilyPond in chroot jail
720 @unnumberedsubsec LilyPond in chroot jail
722 Setting up the server to run LilyPond in a chroot jail is a complicated
723 task. The steps are listed below. Examples in the steps are from
724 Ubuntu GNU/Linux, and may require the use of @code{sudo} as appropriate.
728 @item Install the necessary packages: LilyPond, GhostScript, and ImageMagick.
730 @item Create a new user by the name of @code{lily}:
737 This will create a new group for the @code{lily} user as well, and a
738 home folder, @code{/home/lily}
740 @item In the home folder of the @code{lily} user create a file to use as a
744 dd if=/dev/zero of=/home/lily/loopfile bs=1k count= 200000
748 This example creates a 200MB file for use as the jail filesystem.
750 @item Create a loop device, make a file system and mount it, then create
751 a folder that can be written by the @code{lily} user:
755 losetup /dev/loop0 /home/lily/loopfile
756 mkfs -t ext3 /dev/loop0 200000
757 mount -t ext3 /dev/loop0 /mnt/lilyloop
758 mkdir /mnt/lilyloop/lilyhome
759 chown lily /mnt/lilyloop/lilyhome
762 @item In the configuration of the servers, the JAIL will be @code{/mnt/lilyloop}
763 and the DIR will be @code{/lilyhome}.
765 @item Create a big directory tree in the jail by copying the necessary files, as
766 shown in the sample script below.
768 You can use @code{sed} to create the necessary copy commands for a given
772 for i in "/usr/local/lilypond/usr/bin/lilypond" "/bin/sh" "/usr/bin/; \
773 do ldd $i | sed 's/.*=> \/\(.*\/\)\([^(]*\).*/mkdir -p \1 \&\& \
774 cp -L \/\1\2 \1\2/' | sed 's/\t\/\(.*\/\)\(.*\) (.*)$/mkdir -p \
775 \1 \&\& cp -L \/\1\2 \1\2/' | sed '/.*=>.*/d'; done
780 @subheading Example script for 32-bit Ubuntu 8.04
788 loopdevice=/dev/loop0
789 jaildir=/mnt/lilyloop
790 # the prefix (without the leading slash!)
792 # the directory where lilypond is installed on the system
793 lilydir=/$lilyprefix/lilypond/
795 userhome=$home/$username
796 loopfile=$userhome/loopfile
798 dd if=/dev/zero of=$loopfile bs=1k count=200000
800 losetup $loopdevice $loopfile
801 mkfs -t ext3 $loopdevice 200000
802 mount -t ext3 $loopdevice $jaildir
803 mkdir $jaildir/lilyhome
804 chown $username $jaildir/lilyhome
807 mkdir -p bin usr/bin usr/share usr/lib usr/share/fonts $lilyprefix tmp
810 cp -r -L $lilydir $lilyprefix
811 cp -L /bin/sh /bin/rm bin
812 cp -L /usr/bin/convert /usr/bin/gs usr/bin
813 cp -L /usr/share/fonts/truetype usr/share/fonts
815 # Now the library copying magic
816 for i in "$lilydir/usr/bin/lilypond" "$lilydir/usr/bin/guile" "/bin/sh" \
817 "/bin/rm" "/usr/bin/gs" "/usr/bin/convert"; do ldd $i | sed 's/.*=> \
818 \/\(.*\/\)\([^(]*\).*/mkdir -p \1 \&\& cp -L \/\1\2 \1\2/' | sed \
819 's/\t\/\(.*\/\)\(.*\) (.*)$/mkdir -p \1 \&\& cp -L \/\1\2 \1\2/' \
820 | sed '/.*=>.*/d'; done | sh -s
822 # The shared files for ghostscript...
823 cp -L -r /usr/share/ghostscript usr/share
824 # The shared files for ImageMagick
825 cp -L -r /usr/lib/ImageMagick* usr/lib
827 ### Now, assuming that you have test.ly in /mnt/lilyloop/lilyhome,
828 ### you should be able to run:
829 ### Note that /$lilyprefix/bin/lilypond is a script, which sets the
830 ### LD_LIBRARY_PATH - this is crucial
831 /$lilyprefix/bin/lilypond -jlily,lily,/mnt/lilyloop,/lilyhome test.ly
834 @c " keep quote signs balanced for context-sensitive editors
837 @section Error messages
839 @cindex error messages
840 Different error messages can appear while compiling a file:
846 Something looks suspect. If you are requesting something out of the
847 ordinary then you will understand the message, and can ignore it.
848 However, warnings usually indicate that something is wrong with the
853 Something is definitely wrong. The current processing step (parsing,
854 interpreting, or formatting) will be finished, but the next step will
859 Something is definitely wrong, and LilyPond cannot continue. This
860 happens rarely. The most usual cause is misinstalled fonts.
863 @cindex trace, Scheme
866 Errors that occur while executing Scheme code are caught by the Scheme
867 interpreter. If running with the verbose option (@option{-V} or
868 @option{--verbose}) then a call trace of the offending
869 function call is printed.
871 @item Programming error
872 @cindex Programming error
873 There was some internal inconsistency. These error messages are
874 intended to help the programmers and debuggers. Usually, they can be
875 ignored. Sometimes, they come in such big quantities that they obscure
878 @item Aborted (core dumped)
879 @cindex Aborted (core dumped)
880 This signals a serious programming error that caused the program to
881 crash. Such errors are considered critical. If you stumble on one,
885 @cindex errors, message format
886 If warnings and errors can be linked to some part of the input file,
887 then error messages have the following form
890 @var{filename}:@var{lineno}:@var{columnno}: @var{message}
891 @var{offending input line}
894 A line-break is inserted in the offending line to indicate the column
895 where the error was found. For example,
898 test.ly:2:19: error: not a duration: 5
903 These locations are LilyPond's best guess about where the warning or
904 error occurred, but (by their very nature) warnings and errors occur
905 when something unexpected happens. If you can't see an error in the
906 indicated line of your input file, try checking one or two lines
907 above the indicated position.
909 More information about errors is given in @ref{Common errors}.
913 @section Common errors
915 The error conditions described below occur often, yet the cause
916 is not obvious or easily found. Once seen and understood, they
921 * Music runs off the page::
922 * An extra staff appears::
923 * Error message Unbound variable %::
924 * Error message FT_Get_Glyph_Name::
925 * Warning staff affinities should only decrease::
926 * Error message unexpected \new::
929 @node Music runs off the page
930 @unnumberedsubsec Music runs off the page
932 Music running off the page over the right margin or appearing
933 unduly compressed is almost always due to entering an incorrect
934 duration on a note, causing the final note in a measure to extend
935 over the bar line. It is not invalid if the final note in a
936 measure does not end on the automatically entered bar line, as the
937 note is simply assumed to carry over into the next measure. But
938 if a long sequence of such carry-over measures occurs the music
939 can appear compressed or may flow off the page because automatic
940 line breaks can be inserted only at the end of complete measures,
941 i.e., where all notes end before or at the end of the measure.
943 @warning{An incorrect duration can cause line breaks to be
944 inhibited, leading to a line of highly compressed music or
945 music which flows off the page.}
947 The incorrect duration can be found easily if bar checks are used,
948 see @ruser{Bar and bar number checks}.
950 If you actually intend to have a series of such carry-over measures
951 you will need to insert an invisible bar line where you want the
952 line to break. For details, see @ruser{Bar lines}.
955 @node An extra staff appears
956 @unnumberedsubsec An extra staff appears
958 If contexts are not created explicitly with @code{\new} or
959 @code{\context}, they will be silently created as soon as a
960 command is encountered which cannot be applied to an existing
961 context. In simple scores the automatic creation of contexts is
962 useful, and most of the examples in the LilyPond manuals take
963 advantage of this simplification. But occasionally the silent
964 creation of contexts can give rise to unexpected new staves or
965 scores. For example, it might be expected that the following code
966 would cause all note heads within the following staff to be
967 colored red, but in fact it results in two staves with the note
968 heads remaining the default black in the lower staff.
970 @lilypond[quote,verbatim,relative=2]
971 \override Staff.NoteHead.color = #red
975 This is because a @code{Staff} context does not exist when the
976 override is processed, so one is implicitly created and the override
977 is applied to it, but then the @code{\new Staff} command creates
978 another, separate, staff into which the notes are placed. The
979 correct code to color all note heads red is
981 @lilypond[quote,verbatim,relative=2]
983 \override Staff.NoteHead.color = #red
988 As a second example, if a @code{\relative} command is placed inside
989 a @code{\repeat} command, two staves result, the second offset from
990 the first, because the @code{\repeat} command generates two
991 @code{\relative} blocks, which each implicitly create @code{Staff}
992 and @code{Voice} blocks.
994 @lilypond[quote,verbatim]
996 \relative c' { c4 d e f }
1000 Explicitly instantiating the @code{Voice} context fixes the
1003 @lilypond[quote,verbatim]
1006 \relative c' { c4 d e f }
1012 @node Error message Unbound variable %
1013 @unnumberedsubsec Error message Unbound variable %
1015 This error message will appear at the bottom of the console
1016 output or log file together with a @qq{GUILE signalled an error @dots{}}
1017 message every time a Scheme routine is called which (invalidly)
1018 contains a @emph{LilyPond} rather than a @emph{Scheme} comment.
1020 LilyPond comments begin with a percent sign, (@code{%}), and must
1021 not be used within Scheme routines. Scheme comments begin with a
1022 semi-colon, (@code{;}).
1024 @node Error message FT_Get_Glyph_Name
1025 @unnumberedsubsec Error message FT_Get_Glyph_Name
1027 This error messages appears in the console output or log file if
1028 an input file contains a non-ASCII character and was not saved in
1029 UTF-8 encoding. For details, see @ruser{Text encoding}.
1032 @node Warning staff affinities should only decrease
1033 @unnumberedsubsec Warning staff affinities should only decrease
1034 This warning can appear if there are no staves in the printed
1035 output, for example if there are just a @code{ChordName} context
1036 and a @code{Lyrics} context as in a lead sheet. The warning
1037 messages can be avoided by making one of the contexts behave as a
1041 \override VerticalAxisGroup.staff-affinity = ##f
1045 at its start. For details, see @qq{Spacing of non-staff lines} in
1046 @ruser{Flexible vertical spacing within systems}.
1049 @node Error message unexpected \new
1050 @unnumberedsubsec Error message unexpected @code{\new}
1052 A @code{\score} block must contain a @emph{single} music expression.
1053 If instead it contains several @code{\new Staff},
1054 @code{\new StaffGroup} or similar contexts introduced with @code{\new}
1055 without them being enclosed in either curly brackets,
1056 @code{@{ @dots{} @}}, or double angle brackets, @code{<< @dots{} >>},
1061 % Invalid! Generates error: syntax error, unexpected \new
1062 \new Staff @{ @dots{} @}
1063 \new Staff @{ @dots{} @}
1068 the error message will be produced.
1070 To avoid the error, enclose all the @code{\new} statements in
1071 curly or double angle brackets.
1073 Using curly brackets will introduce the @code{\new} statements
1076 @lilypond[quote,verbatim]
1079 \new Staff { a' a' a' a' }
1080 \new Staff { g' g' g' g' }
1086 but more likely you should be using double angle brackets so the new
1087 staves are introduced in parallel, i.e. simultaneously:
1089 @lilypond[quote,verbatim]
1092 \new Staff { a' a' a' a' }
1093 \new Staff { g' g' g' g' }