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 @chapter Scheme tutorial
19 @cindex Scheme, in-line code
20 @cindex accessing Scheme
21 @cindex evaluating Scheme
24 LilyPond uses the Scheme programming language, both as part of the
25 input syntax, and as internal mechanism to glue modules of the program
26 together. This section is a very brief overview of entering data in
27 Scheme. If you want to know more about Scheme, see
28 @uref{http://@/www@/.schemers@/.org}.
30 LilyPond uses the GNU Guile implementation of Scheme, which is
31 based on the Scheme @qq{R5RS} standard. If you are learning Scheme
32 to use with LilyPond, working with a different implementation (or
33 referring to a different standard) is not recommended. Information
34 on guile can be found at @uref{http://www.gnu.org/software/guile/}.
35 The @qq{R5RS} Scheme standard is located at
36 @uref{http://www.schemers.org/Documents/Standards/R5RS/}.
39 * Introduction to Scheme::
40 * Scheme in LilyPond::
41 * Building complicated functions::
44 @node Introduction to Scheme
45 @section Introduction to Scheme
47 We begin with an introduction to Scheme. For this brief introduction,
48 we will use the GUILE interpreter to explore how the language works.
49 Once we are familiar with Scheme, we will show how the language can
50 be integrated in LilyPond files.
56 * Scheme simple data types::
57 * Scheme compound data types::
58 * Calculations in Scheme::
60 * Scheme conditionals::
64 @subsection Scheme sandbox
66 The LilyPond installation includes the Guile implementation of
67 Scheme. On most systems you can experiment in a Scheme sandbox by
68 opening a terminal window and typing @q{guile}. On some systems,
69 notably Windows, you may need to set the environment variable
70 @code{GUILE_LOAD_PATH} to the directory @code{../usr/shr/guile/1.8}
71 in the LilyPond installation. For the full path to this directory
72 see @rlearning{Other sources of information}. Alternatively, Windows
73 users may simply choose @q{Run} from the Start menu and enter
76 Once the guile sandbox is running, you will receive a guile prompt:
82 You can enter Scheme expressions at this prompt to experiment with Scheme.
84 @node Scheme variables
85 @subsection Scheme variables
87 Scheme variables can have any valid scheme value, including a Scheme
90 Scheme variables are created with @code{define}:
97 Scheme variables can be evaluated at the guile prompt simply by
98 typing the variable name:
106 Scheme variables can be printed on the display by using the display function:
114 Note that both the value @code{2} and the guile prompt @code{guile}
115 showed up on the same line. This can be avoided by calling the
116 newline procedure or displaying a newline character.
119 guile> (display a)(newline)
121 guile> (display a)(display "\n")
126 Once a variable has been created, its value can be changed with @code{set!}:
129 guile> (set! a 12345)
135 @node Scheme simple data types
136 @subsection Scheme simple data types
138 The most basic concept in a language is data typing: numbers, character
139 strings, lists, etc. Here is a list of simple Scheme data types that are
140 often used with LilyPond.
144 Boolean values are True or False. The Scheme for True is @code{#t}
145 and False is @code{#f}.
150 Numbers are entered in the standard fashion,
151 @code{1} is the (integer) number one, while @code{-1.5} is a
152 floating point number (a non-integer number).
155 Strings are enclosed in double quotes:
161 Strings may span several lines:
170 and the newline characters at the end of each line will be included
173 Newline characters can also be added by including @code{\n} in the
177 "this\nis a\nmultiline string"
181 Quotation marks and backslashes are added to strings
182 by preceding them with a backslash.
183 The string @code{\a said "b"} is entered as
191 There are additional Scheme data types that are not discussed here.
192 For a complete listing see the Guile reference guide,
193 @uref{http://www.gnu.org/software/guile/manual/html_node/Simple-Data-Types.html}.
195 @node Scheme compound data types
196 @subsection Scheme compound data types
198 There are also compound data types in Scheme. The types commonly used in
199 LilyPond programming include pairs, lists, alists, and hash tables.
203 The foundational compound data type of Scheme is the @code{pair}. As
204 might be expected from its name, a pair is two values glued together.
205 The operator used to form a pair is called @code{cons}.
213 Note that the pair is displayed as two items surrounded by
214 parentheses and separated by whitespace, a period (@code{.}), and
215 more whitespace. The period is @emph{not} a decimal point, but
216 rather an indicator of the pair.
218 Pairs can also be entered as literal values by preceding them with
219 a single quote character.
227 The two elements of a pair may be any valid Scheme value:
232 guile> '("blah-blah" . 3.1415926535)
233 ("blah-blah" . 3.1415926535)
237 The first and second elements of the pair can be accessed by the
238 Scheme procedures @code{car} and @code{cdr}, respectively.
241 guile> (define mypair (cons 123 "hello there")
252 Note: @code{cdr} is pronounced "could-er", according Sussman and
254 @uref{http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-14.html#footnote_Temp_133}
258 A very common Scheme data structure is the @emph{list}. Formally, a
259 list is defined as either the empty list (represented as @code{'()},
260 or a pair whose @code{cdr} is a list.
262 There are many ways of creating lists. Perhaps the most common is
263 with the @code{list} procedure:
266 guile> (list 1 2 3 "abc" 17.5)
270 As can be seen, a list is displayed in the form of individual elements
271 separated by whitespace and enclosed in parentheses. Unlike a pair,
272 there is no period between the elements.
274 A list can also be entered as a literal list by enclosing its
275 elements in parentheses, and adding a quote:
278 guile> '(17 23 "foo" "bar" "bazzle")
279 (17 23 "foo" "bar" "bazzle")
282 Lists are a central part of Scheme. In, fact, Scheme is considered
283 a dialect of lisp, where @q{lisp} is an abbreviation for
284 @q{List Processing}. Scheme expressions are all lists.
286 @subheading Association lists (alists)
288 A special type of list is an @emph{association list} or @emph{alist}.
289 An alist is used to store data for easy retrieval.
291 Alists are lists whose elements are pairs. The @code{car} of each
292 element is called the @emph{key}, and the @code{cdr} of each element
293 is called the @emph{value}. The Scheme procedure @code{assoc} is
294 used to retrieve an entry from the alist, and @code{cdr} is used to
298 guile> (define my-alist '((1 . "A") (2 . "B") (3 . "C")))
300 ((1 . "A") (2 . "B") (3 . "C"))
301 guile> (assoc 2 my-alist)
303 guile> (cdr (assoc 2 my-alist))
308 Alists are widely used in LilyPond to store properties and other data.
310 @subheading Hash tables
312 A data structure that is used occasionally in LilyPond. A hash table
313 is similar to an array, but the indexes to the array can be any type
314 of Scheme value, not just integers.
316 Hash tables are more efficient than alists if there is a lot of data
317 to store and the data changes very infrequently.
319 The syntax to create hash tables is a bit complex, but you
320 can see examples of it in the LilyPond source.
323 guile> (define h (make-hash-table 10))
326 guile> (hashq-set! h 'key1 "val1")
328 guile> (hashq-set! h 'key2 "val2")
330 guile> (hashq-set! h 3 "val3")
334 Values are retrieved from hash tables with @code{hashq-ref}.
337 guile> (hashq-ref h 3)
339 guile> (hashq-ref h 'key2)
344 Keys and values are retrieved as a pair with @code{hashq-get-handle}.
345 This is a preferred way, because it will return @code{#f} if a key is
349 guile> (hashq-get-handle h 'key1)
351 guile> (hashq-get-handle h 'frob)
356 @node Calculations in Scheme
357 @subsection Calculations in Scheme
360 We have been using lists all along. A calculation, like @code{(+ 1 2)}
361 is also a list (containing the symbol @code{+} and the numbers 1
362 and@tie{}2). Normally lists are interpreted as calculations, and the
363 Scheme interpreter substitutes the outcome of the calculation. To enter a
364 list, we stop the evaluation. This is done by quoting the list with a
365 quote @code{'} symbol. So, for calculations do not use a quote.
367 Inside a quoted list or pair, there is no need to quote anymore. The
368 following is a pair of symbols, a list of symbols and a list of lists
373 #'(staff clef key-signature)
378 Scheme can be used to do calculations. It uses @emph{prefix}
379 syntax. Adding 1 and@tie{}2 is written as @code{(+ 1 2)} rather than the
380 traditional @math{1+2}.
387 Calculations may be nested; the result of a function may
388 be used for another calculation.
395 These calculations are examples of evaluations; an expression like
396 @code{(* 3 4)} is replaced by its value @code{12}.
398 Scheme calculations are sensitive to the differences between integers
399 and non-integers. Integer calculations are exact, while non-integers
400 are calculated to the appropriate limits of precision:
409 When the scheme interpreter encounters an expression that is a list,
410 the first element of the list is treated as a procedure to be
411 evaluated with the arguments of the remainder of the list. Therefore,
412 all operators in Scheme are prefix operators.
414 If the first element of a Scheme expression that is a list passed to
415 the interpreter is @emph{not} an operator or procedure, an error will
425 <unnamed port>:52:1: In expression (1 2 3):
426 <unnamed port>:52:1: Wrong type to apply: 1
431 Here you can see that the interpreter was trying to treat 1 as an
432 operator or procedure, and it couldn't. Hence the error is "Wrong
435 Therefore, to create a list we need to use the list operator, or to
436 quote the list so that the interpreter will not try to evaluate it.
446 This is an error that can appear as you are working with Scheme in LilyPond.
449 The same assignment can be done in completely in Scheme as well,
452 #(define twentyFour (* 2 twelve))
455 @c this next section is confusing -- need to rewrite
457 The @emph{name} of a variable is also an expression, similar to a
458 number or a string. It is entered as
465 @cindex quoting in Scheme
467 The quote mark @code{'} prevents the Scheme interpreter from substituting
468 @code{24} for the @code{twentyFour}. Instead, we get the name
473 @node Scheme procedures
474 @subsection Scheme procedures
476 Scheme procedures are executable scheme expressions that return a
477 value resulting from their execution. They can also manipulate
478 variables defined outside of the procedure.
480 @subheading Defining procedures
482 Procedures are defined in Scheme with define
485 (define (function-name arg1 arg2 ... argn)
486 scheme-expression-that-gives-a-return-value)
489 For example, we could define a procedure to calculate the average:
492 guile> (define (average x y) (/ (+ x y) 2))
494 #<procedure average (x y)>
497 Once a procedure is defined, it is called by putting the procedure
498 name and the arguments in a list. For example, we can calculate
499 the average of 3 and 12:
502 guile> (average 3 12)
506 @subheading Predicates
508 Scheme procedures that return boolean values are often called
509 @emph{predicates}. By convention (but not necessity), predicate names
510 typically end in a question mark:
513 guile> (define (less-than-ten? x) (< x 10))
514 guile> (less-than-ten? 9)
516 guile> (less-than-ten? 15)
520 @subheading Return values
522 Sometimes the user would like to have multiple Scheme expressions in
523 a procedure. There are two ways that multiple expressions can be
524 combined. The first is the @code{begin} procedure, which allows
525 multiple expressions to be evaluated, and returns the value of
529 guile> (begin (+ 1 2) (- 5 8) (* 2 2))
533 The second way to combine multiple expressions is in a @code{let} block.
534 In a let block, a series of bindings are created, and then a sequence
535 of expressions that can include those bindings is evaluated. The
536 return value of the let block is the return value of the last
537 statement in the let block:
540 guile> (let ((x 2) (y 3) (z 4)) (display (+ x y)) (display (- z 4))
541 ... (+ (* x y) (/ z x)))
545 @node Scheme conditionals
546 @subsection Scheme conditionals
550 Scheme has an @code{if} procedure:
553 (if test-expression true-expression false-expression)
556 @var{test-expression} is an expression that returns a boolean
557 value. If @var{test-expression} returns @code{#t}, the if
558 procedure returns the value of @var{true-expression}, otherwise
559 it returns the value of @var{false-expression}.
564 guile> (if (> a b) "a is greater than b" "a is not greater than b")
565 "a is not greater than b"
570 Another conditional procedure in scheme is @code{cond}:
573 (cond (test-expression-1 result-expression-sequence-1)
574 (test-expression-2 result-expression-sequence-2)
576 (test-expression-n result-expression-sequence-n))
584 guile> (cond ((< a b) "a is less than b")
585 ... ((= a b) "a equals b")
586 ... ((> a b) "a is greater than b"))
590 @node Scheme in LilyPond
591 @section Scheme in LilyPond
595 * LilyPond Scheme syntax::
596 * LilyPond variables::
597 * Input variables and Scheme::
598 * Object properties::
599 * LilyPond compound variables::
600 * Internal music representation::
603 @node LilyPond Scheme syntax
604 @subsection LilyPond Scheme syntax
606 The Guile interpreter is part of LilyPond, which means that
607 Scheme can be included in LilyPond input files. The hash mark @code{#}
608 is used to tell the LilyPond parser that the next value is a Scheme
611 Once the parser sees a hash mark, input is passed to the Guile
612 interpreter to evaluate the Scheme expression. The interpreter continues
613 to process input until the end of a Scheme expression is seen.
615 Scheme procedures can be defined in LilyPond input files:
618 #(define (average a b c) (/ (+ a b c) 3))
621 Note that LilyPond comments (@code{%} and @code{%@{ %@}}) cannot
622 be used within Scheme code, even in a LilyPond input file, because
623 the Guile interpreter, not the LilyPond parser, is interpreting
624 the Scheme expression. Comments in Guile Scheme are entered
628 ; this is a single-line comment
631 This a (non-nestable) Guile-style block comment
632 But these are rarely used by Schemers and never in
637 For the rest of this section, we will assume that the data is entered
638 in a music file, so we add @code{#}s at the beginning of each Scheme
641 @node LilyPond variables
642 @subsection LilyPond variables
644 LilyPond variables are stored internally in the form of Scheme
658 This means that LilyPond variables are available
659 for use in Scheme expressions. For example, we could use
662 twentyFour = #(* 2 twelve)
666 which would result in the number 24 being stored in the
667 LilyPond (and Scheme) variable @code{twentyFour}.
669 @node Input variables and Scheme
670 @subsection Input variables and Scheme
672 The input format supports the notion of variables: in the following
673 example, a music expression is assigned to a variable with the name
677 traLaLa = @{ c'4 d'4 @}
682 There is also a form of scoping: in the following example, the
683 @code{\layout} block also contains a @code{traLaLa} variable, which is
684 independent of the outer @code{\traLaLa}.
687 traLaLa = @{ c'4 d'4 @}
688 \layout @{ traLaLa = 1.0 @}
692 In effect, each input file is a scope, and all @code{\header},
693 @code{\midi}, and @code{\layout} blocks are scopes nested inside that
696 Both variables and scoping are implemented in the GUILE module system.
697 An anonymous Scheme module is attached to each scope. An assignment of
701 traLaLa = @{ c'4 d'4 @}
705 is internally converted to a Scheme definition:
708 (define traLaLa @var{Scheme value of `@code{... }'})
711 This means that LilyPond variables and Scheme variables may be freely
712 mixed. In the following example, a music fragment is stored in the
713 variable @code{traLaLa}, and duplicated using Scheme. The result is
714 imported in a @code{\score} block by means of a second variable
718 traLaLa = { c'4 d'4 }
720 %% dummy action to deal with parser lookahead
721 #(display "this needs to be here, sorry!")
723 #(define newLa (map ly:music-deep-copy
724 (list traLaLa traLaLa)))
726 (make-sequential-music newLa))
731 @c Due to parser lookahead
733 In this example, the assignment happens after the parser has
734 verified that nothing interesting happens after
735 @code{traLaLa = @{ ... @}}. Without the dummy statement in the
736 above example, the @code{newLa} definition is executed before
737 @code{traLaLa} is defined, leading to a syntax error.
739 The above example shows how to @q{export} music expressions from the
740 input to the Scheme interpreter. The opposite is also possible. By
741 wrapping a Scheme value in the function @code{ly:export}, a Scheme
742 value is interpreted as if it were entered in LilyPond syntax.
743 Instead of defining @code{\twice}, the example above could also have
748 @{ #(ly:export (make-sequential-music (list newLa))) @}
751 Scheme code is evaluated as soon as the parser encounters it. To
752 define some Scheme code in a macro (to be called later), use
753 @ref{Void functions}, or
757 (ly:set-option 'point-and-click #f))
766 Mixing Scheme and LilyPond variables is not possible with the
767 @code{--safe} option.
770 @node Object properties
771 @subsection Object properties
773 Object properties are stored in LilyPond in the form of alist-chains,
774 which are lists of alists. Properties are set by adding values at
775 the beginning of the property list. Properties are read by retrieving
776 values from the alists.
778 Setting a new value for a property requires assigning a value to
779 the alist with both a key and a value. The LilyPond syntax for doing
783 \override Stem #'thickness = #2.6
786 This instruction adjusts the appearance of stems. An alist entry
787 @code{'(thickness . 2.6)} is added to the property list of the
789 object. @code{thickness} is measured relative to the thickness of
790 staff lines, so these stem lines will be @code{2.6} times the
791 width of staff lines. This makes stems almost twice as thick as their
792 normal size. To distinguish between variables defined in input files (like
793 @code{twentyFour} in the example above) and variables of internal
794 objects, we will call the latter @q{properties} and the former
795 @q{variables.} So, the stem object has a @code{thickness} property,
796 while @code{twentyFour} is a variable.
798 @cindex properties vs. variables
799 @cindex variables vs. properties
801 @c todo -- here we're getting interesting. We're now introducing
802 @c LilyPond variable types. I think this deserves a section all
805 @node LilyPond compound variables
806 @subsection LilyPond compound variables
810 Two-dimensional offsets (X and Y coordinates) are stored as @code{pairs}.
811 The @code{cdr} of the offset is the X coordinate, and the @code{cdr} is
815 \override TextScript #'extra-offset = #'(1 . 2)
818 This assigns the pair @code{(1 . 2)} to the @code{extra-offset}
820 TextScript object. These numbers are measured in staff-spaces, so
821 this command moves the object 1 staff space to the right, and 2 spaces up.
823 Procedures for working with offsets are found in @file{scm/lily-library.scm}.
825 @unnumberedsubsubsec Extents
828 Pairs are also used to store intervals, which represent a range of numbers
829 from the minimum (the @code{car}) to the maximum (the @code{cdr}).
830 Intervals are used to store the X- and Y- extents of printable objects.
831 For X extents, the @code{car} is the left hand X coordinate, and the
832 @code{cdr} is the right hand X coordinate. For Y extents, the @code{car}
833 is the bottom coordinate, and the @code{cdr} is the top coordinate.
835 Procedures for working with intervals are found in
836 @file{scm/lily-library.scm}. These procedures should be used when possible
837 to ensure consistency of code.
839 @unnumberedsubsubsec Property alists
840 @subheading Property alists
842 A property alist is a LilyPond data structure that is an alist whose
843 keys are properties and whose values are Scheme expressions that give
844 the desired value for the property.
846 LilyPond properties are Scheme symbols, such as @code{'thickness}.
848 @unnumberedsubsubsec Alist chains
849 @subheading Alist chains
851 An alist chain is a list containing property alists.
853 The set of all properties that will apply to a grob is typically
854 stored as an alist chain. In order to find the value for a particular
855 property that a grob should have, each alist in the chain is searched in
856 order, looking for an entry containing the property key. The first alist
857 entry found is returned, and the value is the property value.
859 The Shceme procedure @code{chain-assoc-get} is normally used to get
860 grob property values.
862 @node Internal music representation
863 @subsection Internal music representation
865 Internally, music is represented as a Scheme list. The list contains
866 various elements that affect the printed output. Parsing is the process
867 of converting music from the LilyPond input representation to the
868 internal Scheme representation.
870 When a music expression is parsed, it is converted into a set of
871 Scheme music objects. The defining property of a music object is that
872 it takes up time. The time it takes up is called its @emph{duration}.
873 Durations are expressed as a rational number that measures the length
874 of the music object in whole notes.
876 A music object has three kinds of types:
879 music name: Each music expression has a name. For example, a note
880 leads to a @rinternals{NoteEvent}, and @code{\simultaneous} leads to
881 a @rinternals{SimultaneousMusic}. A list of all expressions
882 available is in the Internals Reference manual, under
883 @rinternals{Music expressions}.
886 @q{type} or interface: Each music name has several @q{types} or
887 interfaces, for example, a note is an @code{event}, but it is also a
888 @code{note-event}, a @code{rhythmic-event}, and a
889 @code{melodic-event}. All classes of music are listed in the
890 Internals Reference, under
891 @rinternals{Music classes}.
894 C++ object: Each music object is represented by an object of the C++
898 The actual information of a music expression is stored in properties.
899 For example, a @rinternals{NoteEvent} has @code{pitch} and
900 @code{duration} properties that store the pitch and duration of that
901 note. A list of all properties available can be found in the
902 Internals Reference, under @rinternals{Music properties}.
904 A compound music expression is a music object that contains other
905 music objects in its properties. A list of objects can be stored in
906 the @code{elements} property of a music object, or a single @q{child}
907 music object in the @code{element} property. For example,
908 @rinternals{SequentialMusic} has its children in @code{elements},
909 and @rinternals{GraceMusic} has its single argument in
910 @code{element}. The body of a repeat is stored in the @code{element}
911 property of @rinternals{RepeatedMusic}, and the alternatives in
914 @node Building complicated functions
915 @section Building complicated functions
917 This section explains how to gather the information necessary
918 to create complicated music functions.
921 * Displaying music expressions::
923 * Doubling a note with slurs (example)::
924 * Adding articulation to notes (example)::
927 @node Displaying music expressions
928 @subsection Displaying music expressions
930 @cindex internal storage
931 @cindex displaying music expressions
932 @cindex internal representation, displaying
934 @funindex \displayMusic
936 When writing a music function it is often instructive to inspect how
937 a music expression is stored internally. This can be done with the
938 music function @code{\displayMusic}
942 \displayMusic @{ c'4\f @}
959 (ly:make-duration 2 0 1 1)
961 (ly:make-pitch 0 0 0))
963 'AbsoluteDynamicEvent
968 By default, LilyPond will print these messages to the console along
969 with all the other messages. To split up these messages and save
970 the results of @code{\display@{STUFF@}}, redirect the output to
974 lilypond file.ly >display.txt
977 With a bit of reformatting, the above information is easier to read,
980 (make-music 'SequentialMusic
981 'elements (list (make-music 'EventChord
982 'elements (list (make-music 'NoteEvent
983 'duration (ly:make-duration 2 0 1 1)
984 'pitch (ly:make-pitch 0 0 0))
985 (make-music 'AbsoluteDynamicEvent
989 A @code{@{ ... @}} music sequence has the name @code{SequentialMusic},
990 and its inner expressions are stored as a list in its @code{'elements}
991 property. A note is represented as an @code{EventChord} expression,
992 containing a @code{NoteEvent} object (storing the duration and
993 pitch properties) and any extra information (in this case, an
994 @code{AbsoluteDynamicEvent} with a @code{"f"} text property.
997 @node Music properties
998 @subsection Music properties
1000 The @code{NoteEvent} object is the first object of the
1001 @code{'elements} property of @code{someNote}.
1005 \displayMusic \someNote
1013 (ly:make-duration 2 0 1 1)
1015 (ly:make-pitch 0 0 0))))
1018 The @code{display-scheme-music} function is the function used by
1019 @code{\displayMusic} to display the Scheme representation of a music
1023 #(display-scheme-music (first (ly:music-property someNote 'elements)))
1028 (ly:make-duration 2 0 1 1)
1030 (ly:make-pitch 0 0 0))
1033 Then the note pitch is accessed through the @code{'pitch} property
1034 of the @code{NoteEvent} object,
1037 #(display-scheme-music
1038 (ly:music-property (first (ly:music-property someNote 'elements))
1041 (ly:make-pitch 0 0 0)
1044 The note pitch can be changed by setting this @code{'pitch} property,
1046 @funindex \displayLilyMusic
1049 #(set! (ly:music-property (first (ly:music-property someNote 'elements))
1051 (ly:make-pitch 0 1 0)) ;; set the pitch to d'.
1052 \displayLilyMusic \someNote
1058 @node Doubling a note with slurs (example)
1059 @subsection Doubling a note with slurs (example)
1061 Suppose we want to create a function that translates input like
1062 @code{a} into @code{a( a)}. We begin by examining the internal
1063 representation of the desired result.
1066 \displayMusic@{ a'( a') @}
1077 (ly:make-duration 2 0 1 1)
1079 (ly:make-pitch 0 5 0))
1090 (ly:make-duration 2 0 1 1)
1092 (ly:make-pitch 0 5 0))
1099 The bad news is that the @code{SlurEvent} expressions
1100 must be added @q{inside} the note (or more precisely,
1101 inside the @code{EventChord} expression).
1103 Now we examine the input,
1115 (ly:make-duration 2 0 1 1)
1117 (ly:make-pitch 0 5 0))))))
1120 So in our function, we need to clone this expression (so that we
1121 have two notes to build the sequence), add @code{SlurEvents} to the
1122 @code{'elements} property of each one, and finally make a
1123 @code{SequentialMusic} with the two @code{EventChords}.
1126 doubleSlur = #(define-music-function (parser location note) (ly:music?)
1127 "Return: @{ note ( note ) @}.
1128 `note' is supposed to be an EventChord."
1129 (let ((note2 (ly:music-deep-copy note)))
1130 (set! (ly:music-property note 'elements)
1131 (cons (make-music 'SlurEvent 'span-direction -1)
1132 (ly:music-property note 'elements)))
1133 (set! (ly:music-property note2 'elements)
1134 (cons (make-music 'SlurEvent 'span-direction 1)
1135 (ly:music-property note2 'elements)))
1136 (make-music 'SequentialMusic 'elements (list note note2))))
1140 @node Adding articulation to notes (example)
1141 @subsection Adding articulation to notes (example)
1143 The easy way to add articulation to notes is to merge two music
1144 expressions into one context, as explained in
1145 @ruser{Creating contexts}. However, suppose that we want to write
1146 a music function that does this.
1148 A @code{$variable} inside the @code{#@{...#@}} notation is like
1149 a regular @code{\variable} in classical LilyPond notation. We
1157 will not work in LilyPond. We could avoid this problem by attaching
1158 the articulation to a fake note,
1161 @{ << \music s1*0-.-> @}
1165 but for the sake of this example, we will learn how to do this in
1166 Scheme. We begin by examining our input and desired output,
1178 (ly:make-duration 2 0 1 1)
1180 (ly:make-pitch -1 0 0))))
1191 (ly:make-duration 2 0 1 1)
1193 (ly:make-pitch -1 0 0))
1200 We see that a note (@code{c4}) is represented as an @code{EventChord}
1201 expression, with a @code{NoteEvent} expression in its elements list. To
1202 add a marcato articulation, an @code{ArticulationEvent} expression must
1203 be added to the elements property of the @code{EventChord}
1206 To build this function, we begin with
1209 (define (add-marcato event-chord)
1210 "Add a marcato ArticulationEvent to the elements of `event-chord',
1211 which is supposed to be an EventChord expression."
1212 (let ((result-event-chord (ly:music-deep-copy event-chord)))
1213 (set! (ly:music-property result-event-chord 'elements)
1214 (cons (make-music 'ArticulationEvent
1215 'articulation-type "marcato")
1216 (ly:music-property result-event-chord 'elements)))
1217 result-event-chord))
1220 The first line is the way to define a function in Scheme: the function
1221 name is @code{add-marcato}, and has one variable called
1222 @code{event-chord}. In Scheme, the type of variable is often clear
1223 from its name. (this is good practice in other programming languages,
1231 is a description of what the function does. This is not strictly
1232 necessary, but just like clear variable names, it is good practice.
1235 (let ((result-event-chord (ly:music-deep-copy event-chord)))
1238 @code{let} is used to declare local variables. Here we use one local
1239 variable, named @code{result-event-chord}, to which we give the value
1240 @code{(ly:music-deep-copy event-chord)}. @code{ly:music-deep-copy} is
1241 a function specific to LilyPond, like all functions prefixed by
1242 @code{ly:}. It is use to make a copy of a music
1243 expression. Here we copy @code{event-chord} (the parameter of the
1244 function). Recall that our purpose is to add a marcato to an
1245 @code{EventChord} expression. It is better to not modify the
1246 @code{EventChord} which was given as an argument, because it may be
1249 Now we have a @code{result-event-chord}, which is a
1250 @code{NoteEventChord} expression and is a copy of
1251 @code{event-chord}. We add the marcato to its @code{'elements}
1255 (set! place new-value)
1258 Here, what we want to set (the @q{place}) is the @code{'elements}
1259 property of @code{result-event-chord} expression.
1262 (ly:music-property result-event-chord 'elements)
1265 @code{ly:music-property} is the function used to access music properties
1266 (the @code{'elements}, @code{'duration}, @code{'pitch}, etc, that we
1267 see in the @code{\displayMusic} output above). The new value is the
1268 former @code{'elements} property, with an extra item: the
1269 @code{ArticulationEvent} expression, which we copy from the
1270 @code{\displayMusic} output,
1273 (cons (make-music 'ArticulationEvent
1274 'articulation-type "marcato")
1275 (ly:music-property result-event-chord 'elements))
1278 @code{cons} is used to add an element to a list without modifying
1279 the original list. This is what we want: the same list as before,
1280 plus the new @code{ArticulationEvent} expression. The order
1281 inside the @code{'elements} property is not important here.
1283 Finally, once we have added the marcato articulation to its @code{elements}
1284 property, we can return @code{result-event-chord}, hence the last line of
1287 Now we transform the @code{add-marcato} function into a music
1291 addMarcato = #(define-music-function (parser location event-chord)
1293 "Add a marcato ArticulationEvent to the elements of `event-chord',
1294 which is supposed to be an EventChord expression."
1295 (let ((result-event-chord (ly:music-deep-copy event-chord)))
1296 (set! (ly:music-property result-event-chord 'elements)
1297 (cons (make-music 'ArticulationEvent
1298 'articulation-type "marcato")
1299 (ly:music-property result-event-chord 'elements)))
1300 result-event-chord))
1303 We may verify that this music function works correctly,
1306 \displayMusic \addMarcato c4
1315 * Tweaking with Scheme::
1318 @c @nod e Tweaking with Scheme
1319 @c @sectio n Tweaking with Scheme
1321 We have seen how LilyPond output can be heavily modified using
1323 @code{\override TextScript #'extra-offset = ( 1 . -1)}. But
1324 we have even more power if we use Scheme. For a full explanation
1325 of this, see the @ref{Scheme tutorial}, and
1326 @ref{Interfaces for programmers}.
1328 We can use Scheme to simply @code{\override} commands,
1330 TODO Find a simple example
1331 @c This isn't a valid example with skylining
1332 @c It works fine without padText -td
1336 @lilypond[quote,verbatim,ragged-right]
1337 padText = #(define-music-function (parser location padding) (number?)
1339 \once \override TextScript #'padding = #$padding
1343 c4^"piu mosso" b a b
1345 c4^"piu mosso" d e f
1347 c4^"piu mosso" fis a g
1353 We can use it to create new commands:
1355 @c Check this is a valid example with skylining
1356 @c It is - 'padding still works
1359 @lilypond[quote,verbatim,ragged-right]
1360 tempoPadded = #(define-music-function (parser location padding tempotext)
1363 \once \override Score.MetronomeMark #'padding = $padding
1364 \tempo \markup { \bold $tempotext }
1368 \tempo \markup { "Low tempo" }
1370 \tempoPadded #4.0 #"High tempo"
1376 Even music expressions can be passed in:
1378 @lilypond[quote,verbatim,ragged-right]
1379 pattern = #(define-music-function (parser location x y) (ly:music? ly:music?)
1386 \pattern {d16 dis} { ais16-> b\p }