4 @c A menu is needed before every deeper *section nesting of @nodes
5 @c Run M-x texinfo-all-menus-update
6 @c to automagically fill in these menus
7 @c before saving changes
10 @node Technical manual
11 @chapter Technical manual
14 When LilyPond is run, it reads music from a file, translates that into
15 notation, and outputs the result to a file. The most important steps
16 are the first three. Consequently, there are three important basic
17 concepts within LilyPond: music, translation and layout. The
18 following diagram illustrates the concepts, and list the terminology
19 associated with each step.
24 +-------------+ Translation +----------+
26 | Music | ------------------> | Layout |
28 +-------------+ +----------+
31 Syntax: c4 \context \set #'padding =
34 Objects: Music expressions Contexts Layout object
37 Example objects: NoteEvent Voice NoteHead
40 Example properties: #'pitch keySignature #'line-count
42 User applications: none various tuning layout
46 The objects passed around in LilyPond have @emph{properties},
47 variables that can contain many different types of information. Users
48 can set these variables, to modify the default behavior. Since there
49 are three different main concepts, there are also three types of
53 @cindex concepts, main
55 @cindex music expressions
61 @item Music properties
62 These are used internally, and most users will not see or use them.
64 They use Scheme-style naming, i.e. lowercase words separated with
65 dashes: @code{pitch}, @code{tremolo-type}.
67 @item Translation properties
68 These influence the translation process, and most users will encounter them
69 regularly. For example, beaming behavior is tuned with
70 @code{autoBeamSettings}.
72 These use mixed-caps naming: @code{autoBeamSettings},
73 @code{ignoreMelismata}. They are assigned as follows:
75 \set ignoreMelismata = ...
78 @item Layout properties
79 These are internally used in the formatting process. Consequently, to
80 tune formatting details, it is necessary to adjust these
81 properties. For example, some objects may be moved around vertically
82 by setting their @code{padding} property.
84 These properties use Scheme-style naming: @code{c0-position},
85 @code{break-align-symbol}. They most often assigned as follows:
88 \override Score.RehearsalMark #'break-align-symbol = ...
92 Here, @code{RehearsalMark} is the type of the layout object.
96 This chapter discusses details of the three concepts in more detail,
97 and explains how they are glued together in LilyPond with the embedded
101 * Interpretation context::
102 * Scheme integration::
103 * Music storage format::
109 @node Interpretation context
110 @section Interpretation context
113 * Creating contexts::
115 * Context properties::
116 * Context evaluation::
117 * Defining contexts::
118 * Changing contexts locally::
119 * Engravers and performers::
120 * Defining new contexts::
124 Interpretation contexts are objects that only exist during program
125 run. During the interpretation phase (when @code{interpreting music}
126 is printed on the standard output), the music expression in a
127 @code{\score} block is interpreted in time order, the same order in
128 which we hear and play the music. During this phase, the interpretation
129 context holds the state for the current point within the music, for
132 @item What notes are playing at this point?
134 @item What symbols will be printed at this point?
136 @item What is the current key signature, time signature, point within
140 Contexts are grouped hierarchically: A @internalsref{Voice} context is
141 contained in a @internalsref{Staff} context (because a staff can contain
142 multiple voices at any point), a @internalsref{Staff} context is contained in
143 @internalsref{Score}, @internalsref{StaffGroup}, or
144 @internalsref{ChoirStaff} context.
146 Contexts associated with sheet music output are called @emph{notation
147 contexts}, those for sound output are called @emph{performance
148 contexts}. The default definitions of the standard notation and
149 performance contexts can be found in @file{ly/engraver-init.ly} and
150 @file{ly/performer-init.ly}, respectively.
153 @node Creating contexts
154 @subsection Creating contexts
155 @cindex @code{\context}
156 @cindex context selection
158 Contexts for a music expression can be selected manually, using one of
159 the following music expressions:
162 \new @var{contexttype} @var{musicexpr}
163 \context @var{contexttype} [= @var{contextname}] @var{musicexpr}
167 This means that @var{musicexpr} should be interpreted within a context
168 of type @var{contexttype} (with name @var{contextname} if specified).
169 If no such context exists, it will be created:
171 @lilypond[verbatim,raggedright]
173 \notes \relative c'' {
174 c4 <<d4 \context Staff = "another" e4>> f
180 In this example, the @code{c} and @code{d} are printed on the default
181 staff. For the @code{e}, a context @code{Staff} called @code{another}
182 is specified; since that does not exist, a new context is created.
183 Within @code{another}, a (default) Voice context is created for the
184 @code{e4}. A context is ended when when all music referring it has
185 finished, so after the third quarter, @code{another} is removed.
187 The @code{\new} construction creates a context with a
188 generated, unique @var{contextname}. An expression with
189 @code{\new} always leads to a new context. This is convenient
190 for creating multiple staffs, multiple lyric lines, etc.
192 When using automatic staff changes, automatic phrasing, etc., the
193 context names have special meanings, so @code{\new} cannot be
197 @node Default contexts
198 @subsection Default contexts
200 Every top level music is interpreted by the @code{Score} context; in
201 other words, you may think of @code{\score} working like
205 \context Score @var{music}
209 Music expressions inherit their context from the enclosing music
210 expression. Hence, it is not necessary to explicitly specify
211 @code{\context} for most expressions. In
212 the following example, only the sequential expression has an explicit
213 context. The notes contained therein inherit the @code{goUp} context
214 from the enclosing music expression.
216 @lilypond[verbatim,raggedright]
217 \notes \context Voice = goUp { c'4 d' e' }
221 Second, contexts are created automatically to be able to interpret the
222 music expressions. Consider the following example:
224 @lilypond[verbatim,raggedright]
225 \score { \notes { c'4-( d' e'-) } }
229 The sequential music is interpreted by the Score context initially,
230 but when a note is encountered, contexts are setup to accept that
231 note. In this case, a @code{Voice}, and @code{Staff}
232 context are created. The rest of the sequential music is also
233 interpreted with the same @code{Voice}, and
234 @code{Staff} context, putting the notes on the same staff, in the same
237 @node Context properties
238 @subsection Context properties
240 Contexts have properties. These properties are set from the @file{.ly}
241 file using the following expression:
242 @cindex context properties
243 @cindex properties, context
246 \set @var{contextname}.@var{propname} = @var{value}
250 Sets the @var{propname} property of the context @var{contextname} to
251 the specified Scheme expression @var{value}. Both @var{propname} and
252 @var{contextname} are strings, which can often be written unquoted.
255 Properties that are set in one context are inherited by all of the
256 contained contexts. This means that a property valid for the
257 @internalsref{Voice} context can be set in the @internalsref{Score} context
258 (for example) and thus take effect in all @internalsref{Voice} contexts.
260 Properties can be unset using the following statement.
262 \unset @var{contextname}.@var{propname}
265 @cindex properties, unsetting
266 @cindex @code{\unset}
269 This removes the definition of @var{propname} in @var{contextname}. If
270 @var{propname} was not defined in @var{contextname} (but was inherited
271 from a higher context), then this has no effect.
273 If @var{contextname} is left out, then it defaults to the current
274 ``bottom'' context: this is a context like @internalsref{Voice} that
275 cannot contain any other contexts.
279 @node Context evaluation
280 @subsection Context evaluation
282 Contexts can be modified during interpretation with Scheme code. The
285 \applycontext @var{function}
288 @var{function} should be a Scheme function taking a single argument,
289 being the context to apply it to. The following code will print the
290 current bar number on the standard output during the compile:
295 (format #t "\nWe were called in barnumber ~a.\n"
296 (ly:context-property x 'currentBarNumber)))
301 @node Defining contexts
302 @subsection Defining contexts
304 @cindex context definition
305 @cindex translator definition
307 The most common way to create a new context definition is by extending
308 an existing one. An existing context from the paper block is copied
309 by referencing a context identifier:
314 @var{context-identifier}
320 Every predefined context has a standard identifier. For example, the
321 @code{Staff} context can be referred to as @code{\StaffContext}.
323 The context can then be modified by setting or changing properties,
328 Stem \set #'thickness = #2.0
329 defaultBarType = #"||"
332 These assignments happen before interpretation starts, so a property
333 command will override any predefined settings.
339 It is not possible to collect multiple property assignments in a
340 variable, and apply to one @code{\translator} definition by
341 referencing that variable.
343 @node Changing contexts locally
344 @subsection Changing contexts locally
347 Extending an existing context can also be done locally. A piece of
348 music can be interpreted in a changed context by using the following syntax
352 @var{context modifications}
356 These statements comes between @code{\new} or @code{\context} and the
357 music to be interpreted. The @var{context modifications} property
358 settings and @code{\remove}, @code{\consists} and @code{\consistsend}
359 commands. The syntax is similar to the @code{\translator} block.
361 The following example shows how a staff is created with bigger spaces,
362 and without a @code{Clef_engraver}.
364 @lilypond[relative=1,fragment,verbatim]
366 \new Staff { c4 es4 g2 }
368 \override StaffSymbol #'staff-space = #(magstep 1.5)
370 \remove "Clef_engraver"
378 The command @code{\with} has no effect on contexts that already
382 @node Engravers and performers
383 @subsection Engravers and performers
386 Each context is composed of a number of building blocks, or plug-ins
387 called engravers. An engraver is a specialized C++ class that is
388 compiled into the executable. Typically, an engraver is responsible
389 for one function: the @code{Slur_engraver} creates only @code{Slur}
390 objects, and the @code{Skip_event_swallow_translator} only swallows
391 (silently gobbles) @code{SkipEvent}s.
398 An existing context definition can be changed by adding or removing an
399 engraver. The syntax for these operations is
401 \consists @var{engravername}
402 \remove @var{engravername}
405 @cindex @code{\consists}
406 @cindex @code{\remove}
409 Here @var{engravername} is a string, the name of an engraver in the
410 system. In the following example, the @code{Clef_engraver} is removed
411 from the Staff context. The result is a staff without a clef, where
412 the central C is at its default position, the center line:
414 @lilypond[verbatim,raggedright]
422 \remove Clef_engraver
428 A list of all engravers is in the internal documentation,
429 see @internalsref{Engravers}.
431 @node Defining new contexts
432 @subsection Defining new contexts
435 It is also possible to define new contexts from scratch. To do this,
436 you must define give the new context a name. In the following
437 example, a very simple Staff context is created: one that will put
438 note heads on a staff symbol.
442 \type "Engraver_group_engraver"
445 \consists "Staff_symbol_engraver"
446 \consists "Note_head_engraver"
447 \consistsend "Axis_group_engraver"
452 The argument of @code{\type} is the name for a special engraver that
453 handles cooperation between simple engravers such as
454 @code{Note_head_engraver} and @code{Staff_symbol_engraver}. This
455 should always be @code{Engraver_group_engraver} (unless you are
456 defining a Score context from scratch, in which case
457 @code{Score_engraver} must be used).
459 The complete list of context modifiers is the following:
461 @item @code{\alias} @var{alternate-name}:
462 This specifies a different name. In the above example,
463 @code{\set Staff.X = Y} will also work on @code{SimpleStaff}s.
465 @item @code{\consistsend} @var{engravername}:
466 Analogous to @code{\consists}, but makes sure that
467 @var{engravername} is always added to the end of the list of
470 Engravers that group context objects into axis groups or alignments
471 need to be at the end of the list. @code{\consistsend} insures that
472 engravers stay at the end even if a user adds or removes engravers.
474 @item @code{\accepts} @var{contextname}:
475 This context can contains @var{contextname} contexts. The first
476 @code{\accepts} is created as a default context when events (e.g. notes
477 or rests) are encountered.
479 @item @code{\denies}:
480 The opposite of @code{\accepts}.
482 @item @code{\name} @var{contextname}:
483 This sets the type name of the context, e.g. @code{Staff},
484 @code{Voice}. If the name is not specified, the translator will not
489 @node Scheme integration
490 @section Scheme integration
494 @cindex Scheme, in-line code
495 @cindex accessing Scheme
496 @cindex evaluating Scheme
499 LilyPond internally uses GUILE, a Scheme-interpreter, to represent
500 data throughout the whole program, and glue together different program
501 modules. For advanced usage, it is sometimes necessary to access and
502 program the Scheme interpreter.
504 Scheme is a full-blown programming language, from the LISP
505 family. and a full discussion is outside the scope of this document.
506 Interested readers are referred to the website
507 @uref{http://www.schemers.org/} for more information on Scheme.
509 The GUILE library for extension is documented at
510 @uref{http://www.gnu.org/software/guile}.
512 When it is installed, the following link should take you to its manual
513 @ref{(guile.info)guile}
518 * Input variables and Scheme::
519 * Scheme data types::
524 @subsection Inline Scheme
526 Scheme expressions can be entered in the input file by entering a
527 hash-sign (@code{#}). The expression following the hash-sign is
528 evaluated as Scheme. For example, the boolean value @var{true} is
529 @code{#t} in Scheme, so for LilyPond @var{true} looks like @code{##t},
530 and can be used in property assignments:
532 \set Staff.autoBeaming = ##f
536 @node Input variables and Scheme
537 @subsection Input variables and Scheme
540 The input format supports the notion of variable: in the following
541 example, a music expression is assigned to a variable with the name
544 traLaLa = \notes @{ c'4 d'4 @}
549 There is also a form of scoping: in the following example, the
550 @code{\paper} block also contains a @code{traLaLa} variable, which is
551 independent of the outer @code{\traLaLa}.
553 traLaLa = \notes @{ c'4 d'4 @}
554 \paper @{ traLaLa = 1.0 @}
557 In effect, each input file is a scope, and all @code{\header},
558 @code{\midi} and @code{\paper} blocks are scopes nested inside that
561 Both variables and scoping are implemented in the GUILE module system.
562 An anonymous Scheme module is attached to each scope. An assignment of
565 traLaLa = \notes @{ c'4 d'4 @}
569 is internally converted to a Scheme definition
571 (define traLaLa @var{Scheme value of ``@code{\notes ... }''})
574 This means that input variables and Scheme variables may be freely
575 mixed. In the following example, a music fragment is stored in the
576 variable @code{traLaLa}, and duplicated using Scheme. The result is
577 imported in a @code{\score} by means of a second variable
580 traLaLa = \notes @{ c'4 d'4 @}
582 #(define newLa (map ly:music-deep-copy
583 (list traLaLa traLaLa)))
585 (make-sequential-music newLa))
590 In the above example, music expressions can be `exported' from the
591 input to the Scheme interpreter. The opposite is also possible. By
592 wrapping a Scheme value in the function @code{ly:export}, a Scheme
593 value is interpreted as if it were entered in LilyPond syntax: instead
594 of defining @code{\twice}, the example above could also have been
598 \score @{ #(ly:export (make-sequential-music newLa)) @}
605 @node Scheme data types
606 @subsection Scheme data types
608 Scheme is used to glue together different program modules. To aid this
609 glue function, many LilyPond specific object types can be passed as
612 The following list are all LilyPond specific types, that
613 can exist during parsing:
620 In C++ terms, an @code{Event} is a subtype of @code{Music}. However,
621 both have different functions in the syntax.
622 @item Music_output_def
629 During a run, transient objects are also created and destroyed.
632 @item Grob: short for `Graphical object'.
633 @item Scheme_hash_table
636 @item Stencil: Device-independent page output object,
637 including dimensions.
641 @item Translator: An object that produces audio objects or Grobs.
642 It may be accessed with @code{\applyoutput}.
644 @item Font_metric: An object representing a font.
647 Many functions are defined to manipulate these data structures. They
648 are all listed and documented in the internals manual, see
649 @internalsref{All scheme functions}.
653 @subsection Assignments
656 Variables allow objects to be assigned to names during the parse
657 stage. To assign a variable, use
659 @var{name}@code{=}@var{value}
661 To refer to a variable, precede its name with a backslash:
662 `@code{\}@var{name}'. @var{value} is any valid Scheme value or any of
663 the input-types listed above. Variable assignments can appear at top
664 level in the LilyPond file, but also in @code{\paper} blocks.
666 A variable can be created with any string for its name, but for
667 accessing it in the LilyPond syntax, its name must consist of
668 alphabetic characters only, and may not be a keyword of the syntax.
669 There are no restrictions for naming and accessing variables in the
672 The right hand side of a variable assignment is parsed completely
673 before the assignment is done, so variables may be redefined in terms
674 of its old value, e.g.
680 When a variable is referenced in LilyPond syntax, the information it
681 points to is copied. For this reason, an variable reference must
682 always be the first item in a block.
687 \paperIdent % wrong and invalid
693 \paperIdent % correct
700 @node Music storage format
701 @section Music storage format
703 Music in LilyPond is entered as music expressions. This section
704 discusses different types of music expressions, and explains how
705 information is stored internally. This internal storage is accessible
706 through the Scheme interpreter, so music expressions may be
707 manipulated using Scheme functions.
710 * Music expressions::
711 * Internal music representation::
712 * Manipulating music expressions::
715 @node Music expressions
716 @subsection Music expressions
717 @cindex music expressions
719 Notes, rests, lyric syllables are music expressions. Small music
720 expressions may be combined to form larger ones, for example, by
721 enclosing a list of expressions in @code{\sequential @{ @}} or @code{<<
722 >>}. In the following example, a compound expression is formed out of
723 the quarter note @code{c} and a quarter note @code{d}:
726 \sequential @{ c4 d4 @}
729 @cindex Sequential music
730 @cindex @code{\sequential}
731 @cindex sequential music
734 @cindex Simultaneous music
735 @cindex @code{\simultaneous}
737 The two basic compound music expressions are simultaneous and
741 \sequential @code{@{} @var{musicexprlist} @code{@}}
742 \simultaneous @code{@{} @var{musicexprlist} @code{@}}
745 For both, there is a shorthand:
748 @code{@{} @var{musicexprlist} @code{@}}
755 @code{<<} @var{musicexprlist} @code{>>}
759 for simultaneous music.
760 In principle, the way in which you nest sequential and simultaneous to
761 produce music is not relevant. In the following example, three chords
762 are expressed in two different ways:
764 @lilypond[fragment,verbatim,center,quote]
765 \notes \context Voice {
766 <<a c'>> <<b d'>> <<c' e'>>
767 << { a b c' } { c' d' e' } >>
770 However, using @code{<<} and @code{>>} for entering chords leads to
771 various peculiarities. For this reason, a special syntax
772 for chords was introduced in version 1.7: @code{< >}.
778 Other compound music expressions include:
781 \transpose @var{from} @var{to} @var{expr}
782 \apply @var{func} @var{expr}
783 \context @var{type} = @var{id} @var{expr}
784 \times @var{fraction} @var{expr}
787 @node Internal music representation
788 @subsection Internal music representation
795 When a music expression is parsed, it is converted into a set of
796 Scheme music objects. The defining property of a music object is that
797 it takes up time. Time is a rational number that measures the length
798 of a piece of music, in whole notes.
800 A music object has three kinds of types:
803 music name: Each music expression has a name, for example, a note
804 leads to a @internalsref{NoteEvent}, and @code{\simultaneous} leads to
805 a @internalsref{SimultaneousMusic}. A list of all expressions
806 available is in the internals manual, under @internalsref{Music
810 `type' or interface: Each music name has several `types' or interface,
811 for example, a note is an @code{event}, but it is also a @code{note-event},
812 a @code{rhythmic-event} and a @code{melodic-event}.
814 All classes of music are listed in the internals manual, under
815 @internalsref{Music classes}.
817 C++ object: Each music object is represented by a C++ object. For technical
818 reasons, different music objects may be represented by different C++
819 object types. For example, a note is @code{Event} object, while
820 @code{\grace} creates a @code{Grace_music} object.
822 We expect that distinctions between different C++ types will disappear
826 The actual information of a music expression is stored in properties.
827 For example, a @internalsref{NoteEvent} has @code{pitch} and
828 @code{duration} properties that store the pitch and duration of that
829 note. A list of all properties available is in the internals manual,
830 under @internalsref{Music properties}.
832 A compound music expression is a music object that contains other
833 music objects in its properties. A list of objects can be stored in
834 the @code{elements} property of a music object, or a single `child'
835 music object in the @code{element} object. For example,
836 @internalsref{SequentialMusic} has its children in @code{elements},
837 and @internalsref{GraceMusic} has its single argument in
838 @code{element}. The body of a repeat is in @code{element} property of
839 @internalsref{RepeatedMusic}, and the alternatives in @code{elements}.
841 @node Manipulating music expressions
842 @subsection Manipulating music expressions
844 Music objects and their properties can be accessed and manipulated
845 directly, through the @code{\apply} mechanism.
846 The syntax for @code{\apply} is
848 \apply #@var{func} @var{music}
852 This means that the scheme function @var{func} is called with
853 @var{music} as its argument. The return value of @var{func} is the
854 result of the entire expression. @var{func} may read and write music
855 properties using the functions @code{ly:music-property} and
856 @code{ly:music-set-property!}.
858 An example is a function that reverses the order of elements in
860 @lilypond[verbatim,raggedright]
861 #(define (rev-music-1 m)
862 (ly:music-set-property! m 'elements (reverse
863 (ly:music-property m 'elements)))
865 \score { \notes \apply #rev-music-1 { c4 d4 } }
868 The use of such a function is very limited. The effect of this
869 function is void when applied to an argument which is does not have
870 multiple children. The following function application has no effect:
873 \apply #rev-music-1 \grace @{ c4 d4 @}
877 In this case, @code{\grace} is stored as @internalsref{GraceMusic}, which has no
878 @code{elements}, only a single @code{element}. Every generally
879 applicable function for @code{\apply} must -- like music expressions
880 themselves -- be recursive.
882 The following example is such a recursive function: It first extracts
883 the @code{elements} of an expression, reverses them and puts them
884 back. Then it recurses, both on @code{elements} and @code{element}
887 #(define (reverse-music music)
888 (let* ((elements (ly:music-property music 'elements))
889 (child (ly:music-property music 'element))
890 (reversed (reverse elements)))
893 (ly:music-set-property! music 'elements reversed)
896 (if (ly:music? child) (reverse-music child))
897 (map reverse-music reversed)
902 A slightly more elaborate example is in
903 @inputfileref{input/test,reverse-music.ly}.
905 Some of the input syntax is also implemented as recursive music
906 functions. For example, the syntax for polyphony
912 is actually implemented as a recursive function that replaces the
913 above by the internal equivalent of
915 << \context Voice = "1" @{ \voiceOne a @}
916 \context Voice = "2" @{ \voiceTwo b @} >>
919 Other applications of @code{\apply} are writing out repeats
920 automatically (@inputfileref{input/test,unfold-all-repeats.ly}),
921 saving keystrokes (@inputfileref{input/test,music-box.ly}) and
923 LilyPond input to other formats (@inputfileref{input/test,to-xml.ly})
927 @file{scm/music-functions.scm}, @file{scm/music-types.scm},
928 @inputfileref{input/test,add-staccato.ly},
929 @inputfileref{input/test,unfold-all-repeats.ly}, and
930 @inputfileref{input/test,music-box.ly}.
932 @node Lexical details
933 @section Lexical details
939 By enclosing text in quotes (@code{"}), strings are formed. To
940 include a @code{"} character in a string write @code{\"}. Various
941 other backslash sequences have special interpretations as in the C
942 language. A string that does not contain spaces or special characters
943 can be written without the quotes. The exact form of such unquoted
944 strings depends on the input mode; there are different rules for
945 lyrics, notes and markups. Strings can be concatenated with the
950 @section Output details
952 LilyPond's default output format is @TeX{}. Using the option @option{-f}
953 (or @option{--format}) other output formats can be selected also, but
954 currently none of them work reliably.
956 At the beginning of the output file, various global parameters are defined.
957 It also contains a large @code{\special} call to define PostScript routines
958 to draw items not representable with @TeX{}, mainly slurs and ties. A DVI
959 driver must be able to understand such embedded PostScript, or the output
960 will be rendered incompletely.
962 Then the file @file{lilyponddefs.tex} is loaded to define the macros used
963 in the code which follows. @file{lilyponddefs.tex} includes various other
964 files, partially depending on the global parameters.
966 Now the music is output system by system (a `system' consists of all
967 staves belonging together). From @TeX{}'s point of view, a system is an
968 @code{\hbox} which contains a lowered @code{\vbox} so that it is centered
969 vertically on the baseline of the text. Between systems,
970 @code{\interscoreline} is inserted vertically to have stretchable space.
971 The horizontal dimension of the @code{\hbox} is given by the
972 @code{linewidth} parameter from LilyPond's @code{\paper} block.
975 After the last system LilyPond emits a stronger variant of
976 @code{\interscoreline} only if the macro
977 @code{\lilypondpaperlastpagefill} is not defined (flushing the systems
978 to the top of the page). You can avoid that by setting the variable
979 @code{lastpagefill} in LilyPond's @code{\paper} block.
981 It is possible to fine-tune the vertical offset further by defining the
982 macro @code{\lilypondscoreshift}:
985 \def\lilypondscoreshift@{0.25\baselineskip@}
989 where @code{\baselineskip} is the distance from one text line to the next.
991 The code produced by LilyPond should be run through La@TeX{}, not
994 Here an example how to embed a small LilyPond file @code{foo.ly} into
995 running La@TeX{} text without using the @code{lilypond-book} script
996 (@pxref{lilypond-book manual}):
999 \documentclass@{article@}
1001 \def\lilypondpaperlastpagefill@{@}
1003 \def\lilypondscoreshift@{0.25\baselineskip@}
1006 This is running text which includes an example music file
1012 The file @file{foo.tex} has been simply produced with
1018 It is important to set the @code{indent} parameter to zero in the
1019 @code{\paper} block of @file{foo.ly}.
1021 The call to @code{\lineskip} assures that there is enough vertical space
1022 between the LilyPond box and the surrounding text lines.