Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(981)

Delta Between Two Patch Sets: Documentation/extending/scheme-tutorial.itely

Issue 5341049: Issue 2024: Let #{ ... #} pass its $ handling to environment cloning (Closed)
Left Patch Set: Created 12 years, 4 months ago
Right Patch Set: Ran convert-ly on scm/*.scm, just a single character changed. Created 12 years, 4 months ago
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
Left: Side by side diff | Download
Right: Side by side diff | Download
« no previous file with change/comment | « Documentation/extending/programming-interface.itely ('k') | Documentation/fr/notation/pitches.itely » ('j') | no next file with change/comment »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
LEFTRIGHT
1 @c -*- coding: utf-8; mode: texinfo; -*- 1 @c -*- coding: utf-8; mode: texinfo; -*-
2 2
3 @ignore 3 @ignore
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH 4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 5
6 When revising a translation, copy the HEAD committish of the 6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors' 7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes.. 8 Guide, node Updating translation committishes..
9 @end ignore 9 @end ignore
10 10
(...skipping 743 matching lines...) Expand 10 before | Expand all | Expand 10 after
754 754
755 The above example shows how to @q{export} music expressions from the 755 The above example shows how to @q{export} music expressions from the
756 input to the Scheme interpreter. The opposite is also possible. By 756 input to the Scheme interpreter. The opposite is also possible. By
757 wrapping a Scheme value in the function @code{ly:export}, a Scheme 757 wrapping a Scheme value in the function @code{ly:export}, a Scheme
758 value is interpreted as if it were entered in LilyPond syntax. 758 value is interpreted as if it were entered in LilyPond syntax.
759 Instead of defining @code{\twice}, the example above could also have 759 Instead of defining @code{\twice}, the example above could also have
760 been written as 760 been written as
761 761
762 @example 762 @example
763 ... 763 ...
764 @{ #(ly:export (make-sequential-music (list newLa))) @} 764 @{ $(make-sequential-music (list newLa)) @}
765 @end example 765 @end example
766 766
767 Scheme code is evaluated as soon as the parser encounters it. To 767 Scheme code is evaluated as soon as the parser encounters it. To
768 define some Scheme code in a macro (to be called later), use 768 define some Scheme code in a macro (to be called later), use
769 @ref{Void scheme functions}, or 769 @ref{Void scheme functions}, or
770 770
771 @example 771 @example
772 #(define (nopc) 772 #(define (nopc)
773 (ly:set-option 'point-and-click #f)) 773 (ly:set-option 'point-and-click #f))
774 774
(...skipping 626 matching lines...) Expand 10 before | Expand all | Expand 10 after
1401 #{ 1401 #{
1402 $x e8 a b $y b a e 1402 $x e8 a b $y b a e
1403 #}) 1403 #})
1404 1404
1405 \relative c''{ 1405 \relative c''{
1406 \pattern c8 c8\f 1406 \pattern c8 c8\f
1407 \pattern {d16 dis} { ais16-> b\p } 1407 \pattern {d16 dis} { ais16-> b\p }
1408 } 1408 }
1409 @end lilypond 1409 @end lilypond
1410 @end ignore 1410 @end ignore
LEFTRIGHT

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b