-%% DO NOT EDIT this file manually; it is automatically
-%% generated from LSR http://lsr.dsi.unimi.it
-%% Make any changes in LSR itself, or in Documentation/snippets/new/ ,
-%% and then run scripts/auxiliar/makelsr.py
-%%
-%% This file is in the public domain.
-\version "2.14.2"
+% DO NOT EDIT this file manually; it is automatically
+% generated from Documentation/snippets/new
+% Make any changes in Documentation/snippets/new/
+% and then run scripts/auxiliar/makelsr.py
+%
+% This file is in the public domain.
+%% Note: this file works from version 2.19.21
+\version "2.19.21"
\header {
- lsrtags = "really-cool, pitches, staff-notation, version-specific, contemporary-notation"
+ lsrtags = "contemporary-notation, pitches, really-cool, staff-notation, version-specific"
texidoc = "
-The commonly used @code{\\key} command sets the @code{keySignature}
+The commonly used @code{\\key} command sets the @code{keyAlterations}
property, in the @code{Staff} context.
To create non-standard key signatures, set this property directly. The
format of this command is a list:
-@code{ \\set Staff.keySignature = #`(((octave . step) . alter) ((octave
+@code{ \\set Staff.keyAlterations = #`(((octave . step) . alter) ((octave
. step) . alter) ...) } where, for each element in the list,
@code{octave} specifies the octave (0 being the octave from middle C to
the B above), @code{step} specifies the note within the octave (0 means
C and 6 means B), and @code{alter} is @code{,SHARP ,FLAT ,DOUBLE-SHARP}
-etc. (Note the leading comma.) The accidentals in the key signature
-will appear in the reverse order to that in which they are specified.
+etc. (Note the leading comma.)
Alternatively, for each item in the list, using the more concise format
} % begin verbatim
-\relative c' {
- \set Staff.keySignature = #`(((0 . 6) . ,FLAT)
- ((0 . 5) . ,FLAT)
- ((0 . 3) . ,SHARP))
- c4 d e fis
+
+\relative {
+ \set Staff.keyAlterations = #`((6 . ,FLAT)
+ (5 . ,FLAT)
+ (3 . ,SHARP))
+ c'4 d e fis
aes4 bes c2
}