Make arguments like Context.GrobName accessible as symbol lists

Documentation/learning/tweaks.itely

 @c -*- coding: utf-8; mode: texinfo; -*-
 
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  For details, see the Contributors'
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.16.0"
+@c \version "2.17.6"
 
 @node Tweaking output
 @chapter Tweaking output
 
 This chapter discusses how to modify output.  LilyPond is extremely
 configurable; virtually every fragment of output may be changed.
 
 
 @menu
 * Tweaking basics::
@@ skipping 202 matching lines @@
 most common command used in tweaking, and most of the rest of
 this chapter will be directed to presenting examples of how it is
 used.  Here is a simple example to change the color of the
 note head:
 
 @cindex color property, example
 @cindex NoteHead, example of overriding
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 c4 d
-\override NoteHead #'color = #red
+\override NoteHead.color = #red
 e4 f |
-\override NoteHead #'color = #green
+\override NoteHead.color = #green
 g4 a b c |
 @end lilypond
 
 @strong{\revert command}
 
 @cindex revert command
 
 @funindex \revert
 @funindex revert
 
@@ skipping 11 matching lines @@
 Again, just like @var{Context} in the @code{\override} command,
 @var{Context} is often not needed.  It will be omitted
 in many of the following examples.  Here we revert the color
 of the note head to the default value for the final two notes:
 
 @cindex color property, example
 @cindex NoteHead, example of overriding
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 c4 d
-\override NoteHead #'color = #red
+\override NoteHead.color = #red
 e4 f |
-\override NoteHead #'color = #green
+\override NoteHead.color = #green
 g4 a
-\revert NoteHead #'color
+\revert NoteHead.color
 b4 c |
 @end lilypond
 
 @strong{\once prefix}
 
 @funindex \once
 @funindex once
 
 Both the @code{\override} and the @code{\set} commands may be prefixed
 by @code{\once}.  This causes the following @code{\override} or
 @code{\set} command to be effective only during the current musical
 moment before the property reverts back to its previous value (this can
 be different from the default if another @code{\override} is still in
 effect).  Using the same example, we can change the color of a single
 note like this:
 
 @cindex color property, example
 @cindex NoteHead, example of overriding
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 c4 d
-\override NoteHead #'color = #red
+\override NoteHead.color = #red
 e4 f |
-\once \override NoteHead #'color = #green
+\once \override NoteHead.color = #green
 g4 a
-\revert NoteHead #'color
+\revert NoteHead.color
 b c |
 @end lilypond
 
 @strong{\overrideProperty command}
 
 @cindex overrideProperty command
 
 @funindex \overrideProperty
 @funindex overrideProperty
 
@@ skipping 19 matching lines @@
 
 Here's an example.  Suppose we wish to change the size of the
 middle note head (the E) in a C major chord.  Let's first see what
 @code{\once \override} would do:
 
 @cindex font-size property, example
 @cindex NoteHead, example of overriding
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 <c e g>4
-\once \override NoteHead #'font-size = #-3
+\once \override NoteHead.font-size = #-3
 <c e g>4
 <c e g>4
 @end lilypond
 
 We see the override affects @emph{all} the note heads in the chord.
 This is because all the notes of a chord occur at the same
 @emph{musical moment}, and the action of @code{\once} is to
 apply the override to all layout objects of the type specified
 which occur at the same musical moment as the @code{\override}
 command itself.
 
 The @code{\tweak} command operates in a different way.  It acts on
 the immediately following item in the input stream.  In its simplest
 form, it is effective only on objects which are created directly
 from the following item, essentially note heads and articulations.
 
 So to return to our example, the size of the middle note of
 a chord would be changed in this way:
 
 @cindex font-size property, example
 @cindex @code{\tweak}, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 <c e g>4
-<c \tweak #'font-size #-3 e g>4
+<c \tweak font-size #-3 e g>4
 @end lilypond
 
 Note that the syntax of @code{\tweak} is different from that of the
 @code{\override} command.  The context should not be specified; in
 fact, it would generate an error to do so.  Both context and layout
 object are implied by the following item in the input stream.  Note
 also that an equals sign should not be present.  So the simple form
 of the @code{\tweak} command is
 
 @example
 \tweak #'@var{layout-property} #@var{value}
 @end example
 
 A @code{\tweak} command can also be used to modify just one in
 a series of articulations, as shown here:
 
 @cindex color property, example
 @cindex @code{\tweak}, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 a4^"Black"
-  -\tweak #'color #red ^"Red"
-  -\tweak #'color #green _"Green"
+  -\tweak color #red ^"Red"
+  -\tweak color #green _"Green"
 @end lilypond
 
 @noindent
 Note that the @code{\tweak} command must be preceded by an articulation
 mark since the tweaked expression needs to be applied as an articulation
 itself.  In case of multiple direction overrides (@code{^} or @code{_}),
 the leftmost override wins since it is applied last.
 
 @cindex @code{\tweak}, Accidental
 @cindex @code{\tweak}, specific layout object
 
 Objects such as stems and accidentals are created later, and not
 directly from the following event.  It is still possible to use
 @code{\tweak} on such indirectly created objects by explicitly naming
 the layout object, provided that LilyPond can trace its origin back to
 the original event:
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
-<\tweak Accidental #'color #red   cis4
- \tweak Accidental #'color #green es
+<\tweak Accidental.color #red   cis4
+ \tweak Accidental.color #green es
                                   g>
 @end lilypond
 
 This long form of the @code{\tweak} command can be described as
 @example
 \tweak @var{layout-object} #'@var{layout-property} @var{value}
 @end example
 
 @cindex tuplets, nested
 @cindex triplets, nested
@@ skipping 13 matching lines @@
 distinguish between them.  The first @code{\tweak} command
 specifies that the long tuplet bracket is to be placed above the
 notes and the second one specifies that the tuplet number is to be
 printed in red on the first short tuplet bracket.
 
 @cindex @code{\tweak}, example
 @cindex direction property, example
 @cindex color property, example
 
 @lilypond[quote,ragged-right,verbatim,fragment,relative=2]
-\tweak #'direction #up
+\tweak direction #up
 \times 4/3 {
-  \tweak #'color #red
+  \tweak color #red
   \times 2/3 { c8[ c c] }
   \times 2/3 { c8[ c c] }
   \times 2/3 { c8[ c c] }
 }
 @end lilypond
 
 If nested tuplets do not begin at the same moment, their
 appearance may be modified in the usual way with
 @code{\override} commands:
 
 @cindex text property, example
 @cindex tuplet-number function, example
 @cindex transparent property, example
 @cindex TupletNumber, example of overriding
 
 @c NOTE Tuplet brackets collide if notes are high on staff
 @c See issue 509
 @lilypond[quote,ragged-right,verbatim,fragment,relative=1]
 \times 2/3 { c8[ c c] }
-\once \override TupletNumber
-  #'text = #tuplet-number::calc-fraction-text
+\once \override TupletNumber.text = #tuplet-number::calc-fraction-text
 \times 2/3 {
   c8[ c]
   c8[ c]
-  \once \override TupletNumber #'transparent = ##t
+  \once \override TupletNumber.transparent = ##t
   \times 2/3 { c8[ c c] }
   \times 2/3 { c8[ c c] }
 }
 @end lilypond
 
 
 @seealso
 Notation Reference:
 @ruser{The tweak command}.
 
@@ skipping 112 matching lines @@
 is @code{Slur}, that the name of the property to change is
 @code{thickness} and that the new value should be a number
 somewhat larger than 1.2 if we are to make slurs thicker.
 
 We can now construct the @code{\override} command by simply
 substituting the values we have found for the names, omitting
 the context.  Let's use a very large value for the thickness
 at first, so we can be sure the command is working.  We get:
 
 @example
-\override Slur #'thickness = #5.0
+\override Slur.thickness = #5.0
 @end example
 
 Don't forget the @code{#'} preceding the
 property name and a@tie{}@code{#} preceding the new value!
 
 The final question is, @q{Where should this command be
 placed?}  While you are unsure and learning, the best
 answer is, @q{Within the music, before the first slur and
 close to it.}  Let's do that:
 
 @cindex Slur example of overriding
 @cindex thickness property, example
 
 @lilypond[quote,verbatim,relative=2]
 {
   \key es \major
   \time 6/8
   {
     % Increase thickness of all following slurs from 1.2 to 5.0
-    \override Slur #'thickness = #5.0
+    \override Slur.thickness = #5.0
     r4 bes8 bes[( g]) g |
     g8[( es]) es d[( f]) as |
     as8 g
   }
   \addlyrics {
     The man who | feels love's sweet e -- | mo -- tion
   }
 }
 @end lilypond
 
@@ skipping 49 matching lines @@
 @cindex Slur, example of overriding
 @cindex thickness property, example
 
 @lilypond[quote,verbatim,relative=2]
 {
   \key es \major
   \time 6/8
   {
     r4 bes8
     % Increase thickness of immediately following slur only
-    \once \override Slur #'thickness = #5.0
+    \once \override Slur.thickness = #5.0
     bes8[( g]) g |
     g8[( es]) es d[( f]) as |
     as8 g
   }
   \addlyrics {
     The man who | feels love's sweet e -- | mo -- tion
   }
 }
 @end lilypond
 
@@ skipping 19 matching lines @@
 @cindex Slur, example of overriding
 @cindex thickness property, example
 
 @lilypond[quote,verbatim,relative=2]
 {
   \key es \major
   \time 6/8
   {
     r4 bes8
     % Increase thickness of immediately following slur only
-    \once \override Slur #'thickness = #5.0
+    \once \override Slur.thickness = #5.0
     bes[( g]) g |
     % Increase thickness of immediately following slur only
-    \once \override Slur #'thickness = #5.0
+    \once \override Slur.thickness = #5.0
     g8[( es]) es d[( f]) as |
     as8 g
   }
   \addlyrics {
     The man who | feels love's sweet e -- | mo -- tion
   }
 }
 @end lilypond
 
 @noindent
 or we could omit the @code{\once} command and use the @code{\revert}
 command to return the @code{thickness} property to its default value
 after the second slur:
 
 @cindex Slur, example of overriding
 @cindex thickness property, example
 
 @lilypond[quote,verbatim,relative=2]
 {
   \key es \major
   \time 6/8
   {
     r4 bes8
     % Increase thickness of all following slurs from 1.2 to 5.0
-    \override Slur #'thickness = #5.0
+    \override Slur.thickness = #5.0
     bes[( g]) g |
     g8[( es]) es
     % Revert thickness of all following slurs to default of 1.2
-    \revert Slur #'thickness
+    \revert Slur.thickness
     d8[( f]) as |
     as8 g
   }
   \addlyrics {
     The man who | feels love's sweet e -- | mo -- tion
   }
 }
 @end lilypond
 
 @noindent
@@ skipping 68 matching lines @@
 @code{thickness} or @code{font-shape}, others are used as values that
 can be given to properties, like @code{italic}.  Note the distinction
 from arbitrary text strings, which would appear as @code{"a text
 string"}; for more details about symbols and strings, see
 @rextend{Scheme tutorial}.
 
 So we see that the @code{\override} command needed to print the lyrics
 in italics is:
 
 @example
-\override LyricText #'font-shape = #'italic
+\override LyricText.font-shape = #'italic
 @end example
 
 @noindent
 This should be placed just in front of the lyrics we wish to affect,
 like so:
 
 @cindex font-shape property, example
 @cindex italic, example
 @cindex LyricText, example of overriding
 @cindex @code{\addlyrics}, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \key es \major
   \time 6/8
   {
     r4 bes8 bes[( g]) g |
     g8[( es]) es d[( f]) as |
     as8 g
   }
   \addlyrics {
-    \override LyricText #'font-shape = #'italic
+    \override LyricText.font-shape = #'italic
     The man who | feels love's sweet e -- | mo -- tion
   }
 }
 @end lilypond
 
 @noindent
 and the lyrics are all printed in italics.
 
 @subheading Specifying the context in lyric mode
 
 @cindex context, specifying in lyric mode
 @cindex lyric mode, specifying context
 
 In the case of lyrics, if you try specifying the context in the
 format given earlier the command will fail.  A syllable
 entered in lyricmode is terminated by either a space,
 a newline or a digit.  All other characters are included
 as part of the syllable.  For this reason a space or newline
 must appear before the terminating @code{@}} to prevent it being
 included as part of the final syllable.  Similarly,
 spaces must be inserted before and after the
 period or dot, @q{.}, separating the context name from the
 object name, as otherwise the two names are run together and
 the interpreter cannot recognize them.  So the command should be:
 
 @example
-\override Lyrics . LyricText #'font-shape = #'italic
+\override Lyrics.LyricText.font-shape = #'italic
 @end example
 
 @warning{In lyrics always leave whitespace between the final
 syllable and the terminating brace.}
 
 @warning{In overrides in lyrics always place spaces around
 the dot between the context name and the object name.}
 
 
 @seealso
@@ skipping 127 matching lines @@
 with many other properties, it can be set to print nothing by
 setting its value to @code{#f}.  Let's try it, as before, omitting
 the implied Context, @code{Voice}:
 
 @cindex BarLine, example of overriding
 @cindex stencil property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override BarLine #'stencil = ##f
+  \override BarLine.stencil = ##f
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 The bar lines are still printed.  What is wrong?  Go back to the IR
 and look again at the page giving the properties of BarLine.  At the
 top of the page it says @qq{Barline objects are created by:
 Bar_engraver}.  Go to the @code{Bar_engraver} page.  At the bottom it
 gives a list of Contexts in which the bar engraver operates.  All of
 them are of the type @code{Staff}, so the reason the @code{\override}
 command failed to work as expected is because @code{Barline} is not in
 the default @code{Voice} context.  If the context is specified
 incorrectly, the command simply does not work.  No error message is
 produced, and nothing is logged in the log file.  Let's try correcting
 it by adding the correct context:
 
 @cindex BarLine, example of overriding
 @cindex stencil property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.BarLine #'stencil = ##f
+  \override Staff.BarLine.stencil = ##f
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 Now the bar lines have vanished.
 
 Note, though, that setting the @code{stencil} property to @code{#f}
 will cause errors when the dimensions of the object are required for
 correct processing.  For example, errors will be generated if the
 @code{stencil} property of the @code{NoteHead} object is set to
 @code{#f}.  If this is the case, you can instead use the
 @code{point-stencil} function, which sets the stencil to a object
 with zero size:
 
 @lilypond[quote,verbatim,relative=2]
 {
   c4 c
-  \once \override NoteHead #'stencil = #point-stencil
+  \once \override NoteHead.stencil = #point-stencil
   c4 c
 }
 @end lilypond
 
 @subheading break-visibility
 
 @cindex break-visibility property
 
 We see from the @code{BarLine} properties in the IR that the
 @code{break-visibility} property requires a vector of three booleans.
 These control respectively whether bar lines are printed at the end of
 a line, in the middle of lines, and at the beginning of lines.  For
 our example we want all bar lines to be suppressed, so the value we
 need is @code{'#(#f #f #f)}.  Let's try that, remembering to include
 the @code{Staff} context.  Note also that in writing this value we
 have @code{#'#} before the opening bracket.  The @code{'#} is required
 as part of the value to introduce a vector, and the first@tie{}@code{#} is
 required, as always, to precede the value itself in the
 @code{\override} command.
 
 @cindex BarLine, example of overriding
 @cindex break-visibility property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.BarLine #'break-visibility = #'#(#f #f #f)
+  \override Staff.BarLine.break-visibility = #'#(#f #f #f)
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 And we see this too removes all the bar lines.
 
 @subheading transparent
 
@@ skipping 11 matching lines @@
 also lives in the @code{Staff} context and also supports the
 @code{grob-interface}.  So the command to make the time signature
 transparent is:
 
 @cindex TimeSignature, example of overriding
 @cindex transparent property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.TimeSignature #'transparent = ##t
+  \override Staff.TimeSignature.transparent = ##t
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 @noindent
 The time signature is gone, but this command leaves a gap where
 the time signature should be.  Maybe this is what is wanted for
 an exercise for the student to fill it in, but in other
 circumstances a gap might be undesirable.  To remove it, the
 stencil for the time signature should be set to @code{#f}
 instead:
 
 @cindex TimeSignature, example of overriding
 @cindex stencil property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.TimeSignature #'stencil = ##f
+  \override Staff.TimeSignature.stencil = ##f
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 @noindent
 and the difference is obvious: setting the stencil to @code{#f}
 removes the object entirely; making the object @code{transparent}
 leaves it where it is, but makes it invisible.
@@ skipping 20 matching lines @@
 of the @q{normal} colors listed in the first table in
 @ruser{List of colors}.  To set the bar lines to white
 we write:
 
 @cindex BarLine, example of overriding
 @cindex color property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.BarLine #'color = #white
+  \override Staff.BarLine.color = #white
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 @noindent
 and again, we see the bar lines are not visible.  Note that
 @emph{white} is not preceded by an apostrophe -- it is not
 a symbol, but a @emph{function}.  When called, it provides
@@ skipping 13 matching lines @@
 However, these must be preceded by another function, which
 converts X11 color names into the list of internal values,
 @code{x11-color}, like this:
 
 @cindex BarLine, example of overriding
 @cindex color property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.BarLine #'color = #(x11-color 'white)
+  \override Staff.BarLine.color = #(x11-color 'white)
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 @noindent
 Note that in this case the function @code{x11-color} takes
 a symbol as an argument, so the symbol must be preceded by
 an apostrophe and the two enclosed in brackets.
 
 @cindex rgb colors
 @cindex color, rgb
 
 @funindex rgb-color
 
 There is yet a third function, one which converts RGB values into
 internal colors -- the @code{rgb-color} function.  This takes
 three arguments giving the intensities of the red, green and
 blue colors.  These take values in the range 0 to 1.  So to
 set the color to red the value should be @code{(rgb-color 1 0 0)}
 and to white it should be @code{(rgb-color 1 1 1)}:
 
 @cindex BarLine, example of overriding
 @cindex color property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.BarLine #'color = #(rgb-color 1 1 1)
+  \override Staff.BarLine.color = #(rgb-color 1 1 1)
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 Finally, there is also a grey scale available as part of the
 X11 set of colors.  These range from black, @code{'grey0},
 to white, @code{'grey100}, in steps of 1.  Let's illustrate
 this by setting all the layout objects in our example to
 various shades of grey:
 
 @cindex StaffSymbol, example of overriding
 @cindex TimeSignature, example of overriding
 @cindex Clef, example of overriding
 @cindex NoteHead, example of overriding
 @cindex Stem, example of overriding
 @cindex BarLine, example of overriding
 @cindex color property, example
 @cindex x11-color, example of using
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 {
   \time 12/16
-  \override Staff.StaffSymbol   #'color = #(x11-color 'grey30)
-  \override Staff.TimeSignature #'color = #(x11-color 'grey60)
-  \override Staff.Clef          #'color = #(x11-color 'grey60)
-  \override Voice.NoteHead      #'color = #(x11-color 'grey85)
-  \override Voice.Stem          #'color = #(x11-color 'grey85)
-  \override Staff.BarLine       #'color = #(x11-color 'grey10)
+  \override Staff.StaffSymbol.color = #(x11-color 'grey30)
+  \override Staff.TimeSignature.color = #(x11-color 'grey60)
+  \override Staff.Clef.color = #(x11-color 'grey60)
+  \override Voice.NoteHead.color = #(x11-color 'grey85)
+  \override Voice.Stem.color = #(x11-color 'grey85)
+  \override Staff.BarLine.color = #(x11-color 'grey10)
   c4 b8 c d16 c d8 |
   g,8 a16 b8 c d4 e16 |
   e8
 }
 @end lilypond
 
 @noindent
 Note the contexts associated with each of the layout objects.
 It is important to get these right, or the commands will not
 work!  Remember, the context is the one in which the appropriate
@@ skipping 50 matching lines @@
 \new Staff ="main" {
   \relative g' {
     r4 g8 g c4 c8 d |
     e4 r8
     <<
       { f8 c c }
       \new Staff \with {
         alignAboveContext = #"main"
       }
       {
-        \override Staff.Clef #'stencil = ##f
-        \override Staff.TimeSignature #'stencil = ##f
+        \override Staff.Clef.stencil = ##f
+        \override Staff.TimeSignature.stencil = ##f
         { f8 f c }
       }
     >>
     r4 |
   }
 }
 @end lilypond
 
 @noindent
 where the extra pair of braces after the @code{\with} clause are
@@ skipping 38 matching lines @@
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \new Staff ="main" {
   \relative g' {
     r4 g8 g c4 c8 d |
     e4 r8
     <<
       { f8 c c }
       \new Staff \with {
         alignAboveContext = #"main"
         % Don't print clefs in this staff
-        \override Clef #'stencil = ##f
+        \override Clef.stencil = ##f
         % Don't print time signatures in this staff
-        \override TimeSignature #'stencil = ##f
+        \override TimeSignature.stencil = ##f
       }
       { f8 f c }
     >>
     r4 |
   }
 }
 @end lilypond
 
 Finally we come to changing the size of layout objects.
 
 Some layout objects are created as glyphs selected from a typeface
 font.  These include note heads, accidentals, markup, clefs, time
 signatures, dynamics and lyrics.  Their size is changed by modifying
 the @code{font-size} property, as we shall shortly see.  Other layout
 objects such as slurs and ties -- in general, spanner objects -- are
 drawn individually, so there is no @code{font-size} associated with
 them.  These objects generally derive their size from the objects to
 which they are attached, so usually there is no need to change their
 size manually.  Still other properties such as the length of stems and
 bar lines, thickness of beams and other lines, and the separation of
 staff lines all need to be modified in special ways.
 
 Returning to the ossia example, let us first change the font-size.
 We can do this in two ways.  We can either change the size of the
 fonts of each object type, like @code{NoteHead}s with commands
 like
 
 @example
-\override NoteHead #'font-size = #-2
+\override NoteHead.font-size = #-2
 @end example
 
 or we can change the size of all fonts by setting a special
 property, @code{fontSize}, using @code{\set}, or by including
 it in a @code{\with} clause (but without the @code{\set}).
 
 @example
 \set fontSize = #-2
 @end example
 
@@ skipping 11 matching lines @@
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \new Staff ="main" {
   \relative g' {
     r4 g8 g c4 c8 d |
     e4 r8
     <<
       { f8 c c }
       \new Staff \with {
         alignAboveContext = #"main"
-        \override Clef #'stencil = ##f
-        \override TimeSignature #'stencil = ##f
+        \override Clef.stencil = ##f
+        \override TimeSignature.stencil = ##f
         % Reduce all font sizes by ~24%
         fontSize = #-2
       }
       { f8 f c }
     >>
     r4 |
   }
 }
 @end lilypond
 
@@ skipping 44 matching lines @@
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \new Staff ="main" {
   \relative g' {
     r4 g8 g c4 c8 d |
     e4 r8
     <<
       { f8 c c }
       \new Staff \with {
         alignAboveContext = #"main"
-        \override Clef #'stencil = ##f
-        \override TimeSignature #'stencil = ##f
+        \override Clef.stencil = ##f
+        \override TimeSignature.stencil = ##f
         fontSize = #-2
         % Reduce stem length and line spacing to match
-        \override StaffSymbol #'staff-space = #(magstep -2)
+        \override StaffSymbol.staff-space = #(magstep -2)
       }
       { f8 f c }
     >>
     r4 |
   }
 }
 @end lilypond
 
 @noindent
 Since the length of stems and many other length-related properties are
@@ skipping 135 matching lines @@
 with those on high notes pointing down and those on low notes pointing
 up, followed by four notes with all stems forced down, four notes with
 all stems forced up, and finally four notes reverted back to the
 default behavior.
 
 @cindex Stem, example of overriding
 @cindex direction property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 a4 g c a |
-\override Stem #'direction = #DOWN
+\override Stem.direction = #DOWN
 a4 g c a |
-\override Stem #'direction = #UP
+\override Stem.direction = #UP
 a4 g c a |
-\revert Stem #'direction
+\revert Stem.direction
 a4 g c a |
 @end lilypond
 
 Here we use the constants @code{DOWN} and @code{UP}.
 These have the values @w{@code{-1}} and @code{+1} respectively, and
 these numerical values may be used instead.  The value @code{0}
 may also be used in some cases.  It is simply treated as meaning
 @code{UP} for stems, but for some objects it means @q{center}.
 There is a constant, @code{CENTER} which has the value @code{0}.
 
@@ skipping 66 matching lines @@
 First, here's the effect of @code{direction} on the fingering
 attached to single notes.  The first bar shows the default
 behaviour, and the following two bars shows the effect of
 specifying @code{DOWN} and @code{UP}:
 
 @cindex Fingering, example of overriding
 @cindex direction property, example
 
 @lilypond[quote,verbatim,relative=2]
 c4-5 a-3 f-1 c'-5 |
-\override Fingering #'direction = #DOWN
+\override Fingering.direction = #DOWN
 c4-5 a-3 f-1 c'-5 |
-\override Fingering #'direction = #UP
+\override Fingering.direction = #UP
 c4-5 a-3 f-1 c'-5 |
 @end lilypond
 
 However, overriding the @code{direction} property is not the
 easiest way of manually setting the fingering above or below
 the notes; using @code{_} or @code{^} instead of @code{-} before
 the fingering number is usually preferable.  Here is the previous
 example using this method:
 
 @cindex fingering example
@@ skipping 82 matching lines @@
 <c-1 e-2 g-3 b-5>4
 @end lilypond
 
 @noindent
 If the fingering seems a little crowded the @code{font-size}
 could be reduced.  The default value can be seen from the
 @code{Fingering} object in the IR to be @w{@code{-5}}, so let's
 try @w{@code{-7}}:
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
-\override Fingering #'font-size = #-7
+\override Fingering.font-size = #-7
 \set fingeringOrientations = #'(left)
 <f-2>4
 <c-1 e-2 g-3 b-5>4
 \set fingeringOrientations = #'(left)
 <f-2>4
 <c-1 e-2 g-3 b-5>4 |
 \set fingeringOrientations = #'(up left down)
 <f-2>4
 <c-1 e-2 g-3 b-5>4
 \set fingeringOrientations = #'(up left)
@@ skipping 77 matching lines @@
 @funindex \startTextSpan
 @funindex startTextSpan
 @funindex \stopTextSpan
 @funindex stopTextSpan
 
 @cindex TextSpanner, example of overriding
 @cindex bound-details property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 % Set details for later Text Spanner
-\override TextSpanner #'(bound-details left text)
+\override TextSpanner.bound-details.left.text
     = \markup { \small \bold Slower }
 % Place dynamics above staff
 \dynamicUp
 % Start Ottava Bracket
 \ottava #1
 c'4 \startTextSpan
 % Add Dynamic Text and hairpin
 c4\pp\<
 c4
 % Add Text Script
@@ skipping 29 matching lines @@
 look up the priority of @code{OttavaBracket} in the IR or in the
 tables above, and reduce it to a value lower than that of a
 @code{TextSpanner}, remembering that @code{OttavaBracket} is created
 in the @code{Staff} context:
 
 @cindex TextSpanner, example of overriding
 @cindex bound-details property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=1]
 % Set details for later Text Spanner
-\override TextSpanner #'(bound-details left text)
+\override TextSpanner.bound-details.left.text
     = \markup { \small \bold Slower }
 % Place dynamics above staff
 \dynamicUp
 % Place following Ottava Bracket below Text Spanners
-\once \override Staff.OttavaBracket #'outside-staff-priority = #340
+\once \override Staff.OttavaBracket.outside-staff-priority = #340
 % Start Ottava Bracket
 \ottava #1
 c'4 \startTextSpan
 % Add Dynamic Text
 c4\pp
 % Add Dynamic Line Spanner
 c4\<
 % Add Text Script
 c4^Text |
 c4 c
@@ skipping 22 matching lines @@
 inside the slur, but the @code{avoid-slur} property is effective
 only if the @code{outside-staff-priority} is also set to @code{#f}.
 Alternatively, the @code{outside-staff-priority} of the slur
 can be set to a numerical value to cause it to be placed along with
 other outside-staff objects according to that value.  Here's an
 example showing the effect of the two methods:
 
 @lilypond[quote,verbatim,relative=2]
 c4( c^\markup { \tiny \sharp } d4.) c8 |
 c4(
-\once \override TextScript #'avoid-slur = #'inside
-\once \override TextScript #'outside-staff-priority = ##f
+\once \override TextScript.avoid-slur = #'inside
+\once \override TextScript.outside-staff-priority = ##f
 c4^\markup { \tiny \sharp } d4.) c8 |
-\once \override Slur #'outside-staff-priority = #500
+\once \override Slur.outside-staff-priority = #500
 c4( c^\markup { \tiny \sharp } d4.) c8 |
 @end lilypond
 
 Changing the @code{outside-staff-priority} can also be used to
 control the vertical placement of individual objects, although
 the results may not always be desirable.  Suppose we would
 like @qq{Text3} to be placed above @qq{Text4} in the example
 under Automatic behavior, above (see @ref{Automatic behavior}).
 All we need to do is to look up the priority of @code{TextScript}
 in the IR or in the tables above, and increase the priority of
 @qq{Text3} to a higher value:
 
 @cindex TextScript, example of overriding
 @cindex outside-staff-priority property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 c2^"Text1"
 c2^"Text2" |
-\once \override TextScript #'outside-staff-priority = #500
+\once \override TextScript.outside-staff-priority = #500
 c2^"Text3"
 c2^"Text4" |
 @end lilypond
 
 This certainly lifts @qq{Text3} above @qq{Text4} but it also lifts it
 above @qq{Text2}, and @qq{Text4} now drops down.  Perhaps this is not
 so good.  What we would really like to do is to position all the
 annotation at the same distance above the staff.  To do this, we
 clearly will need to space the notes out horizontally to make more
 room for the text.  This is done using the @code{textLengthOn}
@@ skipping 39 matching lines @@
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 % This markup is short enough to fit without collision
 c2^"Tex" c'' |
 R1 |
 
 % This is too long to fit, so it is displaced upwards
 c,,2^"Text" c'' |
 R1 |
 
 % Turn off collision avoidance
-\once \override TextScript #'outside-staff-priority = ##f
+\once \override TextScript.outside-staff-priority = ##f
 c,,2^"Long Text   " c'' |
 R1 |
 
 % Turn off collision avoidance
-\once \override TextScript #'outside-staff-priority = ##f
+\once \override TextScript.outside-staff-priority = ##f
 \textLengthOn        % and turn on textLengthOn
 c,,2^"Long Text   "  % Spaces at end are honored
 c''2 |
 @end lilypond
 
 
 @subheading Dynamics
 
 @cindex tweaking dynamics placement
 @cindex dynamics, tweaking placement
@@ skipping 57 matching lines @@
 that they may overlap in the horizontal direction.  This is done
 by the trick of adding infinity to the leftmost extent and
 minus infinity to the rightmost extent by setting the
 @code{extra-spacing-width} to @code{'(+inf.0 . -inf.0)}.  So
 to ensure they do not overlap in the horizontal direction we
 must override this value of @code{extra-spacing-width} to
 @code{'(0 . 0)} so the true width shines through.  This is
 the command to do this for dynamic text:
 
 @example
-\override DynamicText #'extra-spacing-width = #'(0 . 0)
+\override DynamicText.extra-spacing-width = #'(0 . 0)
 @end example
 
 @noindent
 Let's see if this works in our previous example:
 
 @cindex DynamicText, example of overriding
 @cindex extra-spacing-width property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \dynamicUp
-\override DynamicText #'extra-spacing-width = #'(0 . 0)
+\override DynamicText.extra-spacing-width = #'(0 . 0)
 a4\f b\mf c\mp b\p |
 @end lilypond
 
 @noindent
 Well, it has certainly stopped the dynamic marks being
 displaced, but two problems remain.  The marks should be
 spaced a little further apart and it would be better
 if they were all the same distance from the staff.
 We can solve the first problem easily.  Instead of making
 the @code{extra-spacing-width} zero we could add a little
 more to it.  The units are the space between two staff
 lines, so moving the left edge half a unit to the left and the
 right edge half a unit to the right should do it:
 
 @cindex DynamicText, example of overriding
 @cindex extra-spacing-width property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \dynamicUp
 % Extend width by 1 staff space
-\override DynamicText #'extra-spacing-width = #'(-0.5 . 0.5)
+\override DynamicText.extra-spacing-width = #'(-0.5 . 0.5)
 a4\f b\mf c\mp b\p
 @end lilypond
 
 @noindent
 This looks better, but maybe we would prefer the dynamic marks
 to be aligned along the same baseline rather than going up and
 down with the notes.  The property to do this is
 @code{staff-padding} which is covered in the following section.
 
 
@@ skipping 250 matching lines @@
 
 The @code{padding} property can be set to increase
 (or decrease) the distance between symbols that are printed
 above or below notes.
 
 @cindex Script, example of overriding
 @cindex padding property, example
 
 @lilypond[quote,fragment,relative=1,verbatim]
 c2\fermata
-\override Script #'padding = #3
+\override Script.padding = #3
 b2\fermata
 @end lilypond
 
 @cindex MetronomeMark, example of overriding
 @cindex padding property, example
 
 @lilypond[quote,fragment,relative=1,verbatim]
 % This will not work, see below
-\override MetronomeMark #'padding = #3
+\override MetronomeMark.padding = #3
 \tempo 4 = 120
 c1 |
 % This works
-\override Score.MetronomeMark #'padding = #3
+\override Score.MetronomeMark.padding = #3
 \tempo 4 = 80
 d1 |
 @end lilypond
 
 Note in the second example how important it is to figure out what
 context handles a certain object.  Since the @code{MetronomeMark}
 object is handled in the @code{Score} context, property changes in the
 @code{Voice} context will not be noticed.  For more details, see
 @ruser{Modifying properties}.
 
@@ skipping 18 matching lines @@
 @cindex text property, example
 @cindex stencil property, example
 @cindex AccidentalPlacement, example of overriding
 @cindex right-padding property, example
 
 @lilypond[quote,ragged-right,verbatim]
 sesquisharp = \markup { \sesquisharp }
 \relative c'' {
   c4
   % This prints a sesquisharp but the spacing is too small
-  \once \override Accidental
-    #'stencil = #ly:text-interface::print
-  \once \override Accidental #'text = #sesquisharp
+  \once \override Accidental.stencil = #ly:text-interface::print
+  \once \override Accidental.text = #sesquisharp
   cis4 c
   % This improves the spacing
-  \once \override Score.AccidentalPlacement #'right-padding = #0.6
-  \once \override Accidental
-    #'stencil = #ly:text-interface::print
-  \once \override Accidental #'text = #sesquisharp
+  \once \override Score.AccidentalPlacement.right-padding = #0.6
+  \once \override Accidental.stencil = #ly:text-interface::print
+  \once \override Accidental.text = #sesquisharp
   cis4 |
 }
 @end lilypond
 
 @noindent
 This necessarily uses an override for the accidental stencil which
 will not be covered until later.  The stencil type must be a
 procedure, here changed to print the contents of the @code{text}
 property of @code{Accidental}, which itself is set to be a
 sesquisharp sign.  This sign is then moved further away from the
@@ skipping 16 matching lines @@
 example taken from the previous section:
 
 @cindex DynamicText, example of overriding
 @cindex extra-spacing-width property, example
 @cindex DynamicLineSpanner, example of overriding
 @cindex staff-padding property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=2]
 \dynamicUp
 % Extend width by 1 unit
-\override DynamicText #'extra-spacing-width = #'(-0.5 . 0.5)
+\override DynamicText.extra-spacing-width = #'(-0.5 . 0.5)
 % Align dynamics to a base line 2 units above staff
-\override DynamicLineSpanner #'staff-padding = #2
+\override DynamicLineSpanner.staff-padding = #2
 a4\f b\mf c\mp b\p
 @end lilypond
 
 
 @subheading self-alignment-X property
 
 The following example shows how this can resolve the collision
 of a string fingering object with a note's stem by aligning the
 right edge with the reference point of the parent note:
 
 @cindex StringNumber, example of overriding
 @cindex self-alignment-X property, example
 
 @lilypond[quote,fragment,ragged-right,verbatim,relative=3]
 \voiceOne
 <a\2>
-\once \override StringNumber #'self-alignment-X = #RIGHT
+\once \override StringNumber.self-alignment-X = #RIGHT
 <a\2>
 @end lilypond
 
 @subheading staff-position property
 
 @cindex object collision within a staff
 
 Multimeasure rests in one voice can collide with notes in another.
 Since these rests are typeset centered between the bar lines, it
 would require significant effort for LilyPond to figure out which
@@ skipping 12 matching lines @@
 @code{staff-position} is set to -4 for MultiMeasureRest, so we need to
 move it, say, four half-staff spaces down to @w{@code{-8}}.
 
 @cindex MultiMeasureRest, example of overriding
 @cindex staff-position property, example
 
 @lilypond[quote,verbatim,fragment,ragged-right, relative=1]
 <<
   { c4 c c c }
   \\
-  \override MultiMeasureRest #'staff-position = #-8
+  \override MultiMeasureRest.staff-position = #-8
   { R1 }
 >>
 @end lilypond
 
 This is better than using, for example, @code{extra-offset},
 because the ledger line above the rest is inserted automatically.
 
 @subheading extra-offset property
 
 @cindex positioning objects
 @cindex positioning grobs
 @cindex objects, positioning
 @cindex grobs, positioning
 
 The @code{extra-offset} property provides complete control over the
 positioning of an object both horizontally and vertically.
 
 In the following example, the second fingering is moved a little to
 the left, and 1.8 staff space downwards:
 
 @cindex Fingering, example of overriding
 @cindex extra-offset property, example
 
 @lilypond[quote,fragment,relative=1,verbatim]
 \stemUp
 f4-5
-\once \override Fingering #'extra-offset = #'(-0.3 . -1.8)
+\once \override Fingering.extra-offset = #'(-0.3 . -1.8)
 f4-5
 @end lilypond
 
 
 @subheading positions property
 
 @cindex controlling tuplets, slurs, phrasing slurs, and beams manually
 @cindex manually controlling tuplets, slurs, phrasing slurs, and beams
 @cindex tuplet beams, controlling manually
 @cindex slurs, controlling manually
@@ skipping 23 matching lines @@
 But if there were some reason why this could not be done the
 other alternative would be to move the left end of the phrasing
 slur down a little using the @code{positions} property.  This
 also resolves the rather nasty shape.
 
 @cindex PhrasingSlur, example of overriding
 @cindex positions property, example
 
 @lilypond[quote,verbatim,fragment,ragged-right,relative=1]
 r4
-\once \override PhrasingSlur #'positions = #'(-4 . -3)
+\once \override PhrasingSlur.positions = #'(-4 . -3)
 \acciaccatura e8\( d8 c~ c d c d\)
 @end lilypond
 
 Here's a further example.  We see that the beams
 collide with the ties:
 
 @lilypond[quote,verbatim,fragment,ragged-right]
 {
   \time 4/2
   <<
@@ skipping 17 matching lines @@
 @cindex Beam, example of overriding
 @cindex positions property, example
 
 @lilypond[quote,verbatim,fragment,ragged-right]
 {
   \time 4/2
   <<
     { c'1 ~ c'2. e'8 f' }
     \\
     {
-      \override Beam #'positions = #'(-1 . -1)
+      \override Beam.positions = #'(-1 . -1)
       e''8 e'' e'' e''  e'' e'' e'' e''  f''2 g''
     }
   >>
   <<
     { c'1 ~ c'2. e'8 f' }
     \\
     { e''8 e'' e'' e''  e'' e'' e'' e''  f''2 g'' }
   >>
 }
 @end lilypond
@@ skipping 42 matching lines @@
 @cindex force-hshift property, example
 
 @lilypond[quote,verbatim,fragment,ragged-right]
 \new Staff \relative c'' {
   \key aes \major
   <<
     { c2 aes4. bes8 }
     \\
     {
       <ees, c>2
-      \once \override NoteColumn #'force-hshift = #0.5
+      \once \override NoteColumn.force-hshift = #0.5
       des2
     }
     \\
     \\
     {
-      \override NoteColumn #'force-hshift = #0
+      \override NoteColumn.force-hshift = #0
       aes'2 f4 fes
     }
   >> |
   <c ees aes c>1 |
 }
 @end lilypond
 
 
 @node Real music example
 @subsection Real music example
@@ skipping 12 matching lines @@
 over-complicating the example too much we have left out the
 dynamics, fingering and pedalling.
 
 @c The following should appear as music without code
 @c This example should not be indexed
 @c line-width ensures no break
 @lilypond[quote,ragged-right,line-width=6\in]
 rhMusic = \relative c'' {
   \new Voice {
     r2 c4.\( g8 |
-    \once \override Tie #'staff-position = #3.5
+    \once \override Tie.staff-position = #3.5
     bes1~ |
     \bar "||"
     \time 6/4
     \mergeDifferentlyHeadedOn
     \mergeDifferentlyDottedOn
     bes2.^\markup { \bold "Moderato" } r8
     <<
       { c,8 d fis bes a }
       \new Voice {
         \voiceTwo
         c,8~
         % Reposition the c2 to the right of the merged note
-        \once \override NoteColumn #'force-hshift = #1.0
+        \once \override NoteColumn.force-hshift = #1.0
         % Move the c2 out of the main note column
         % so the merge will work
         \shiftOnn
         c2
       }
       \new Voice {
         \voiceThree
         s8
         % Stem on the d2 must be down to permit merging
         \stemDown
         % Stem on the d2 should be invisible
-        \tweak Stem #'transparent ##t
-        \tweak Flag #'transparent ##t
+        \tweak Stem.transparent ##t
+        \tweak Flag.transparent ##t
         d2
       }
       \new Voice {
         \voiceFour
         s4 fis4.
       }
     >> |
     \mergeDifferentlyHeadedOff
     \mergeDifferentlyDottedOff
     g2.\)
@@ skipping 155 matching lines @@
 produced by the @code{\bar "||"} command.  That's easily done.  We
 next need to correct the collision of the tie with the time signature.
 This is best done by moving the tie upwards.  Moving objects was
 covered earlier in @ref{Moving objects}, which says that objects
 positioned relative to the staff can be moved vertically by overriding
 their @code{staff-position} property, which is specified in half staff
 spaces relative to the center line of the staff.  So the following
 override placed just before the first tied note would move the tie up
 to 3.5 half staff spaces above the center line:
 
-@code{\once \override Tie #'staff-position = #3.5}
+@code{\once \override Tie.staff-position = #3.5}
 
 This completes bar two, giving:
 
 @c line-width ensures no break
 @lilypond[quote,verbatim,ragged-right,line-width=6\in]
 rhMusic = \relative c'' {
   \new Voice {
     r2 c4.\( g8 |
-    \once \override Tie #'staff-position = #3.5
+    \once \override Tie.staff-position = #3.5
     bes1~ |
     \bar "||"
     \time 6/4
     bes2. r8
     % Start polyphonic section of four voices
     <<
       { c,8 d fis bes a }  % continuation of main voice
       \new Voice {
         \voiceTwo
         c,8~ c2
@@ skipping 58 matching lines @@
 @end example
 
 @noindent
 to the end, giving:
 
 @c line-width ensures no break
 @lilypond[quote,ragged-right,line-width=6\in]
 rhMusic = \relative c'' {
   \new Voice {
     r2 c4.\( g8 |
-    \once \override Tie #'staff-position = #3.5
+    \once \override Tie.staff-position = #3.5
     bes1~ |
     \bar "||"
     \time 6/4
     bes2.^\markup { \bold "Moderato" } r8
     \mergeDifferentlyHeadedOn
     \mergeDifferentlyDottedOn
     % Start polyphonic section of four voices
     <<
       { c,8 d fis bes a }  % continuation of main voice
       \new Voice {
@@ skipping 53 matching lines @@
 Applying these changes gives:
 
 @cindex Tie, example of overriding
 @cindex staff-position property, example
 
 @c line-width ensures no break
 @lilypond[quote,verbatim,ragged-right,line-width=6\in]
 rhMusic = \relative c'' {
   \new Voice {
     r2 c4.\( g8 |
-    \once \override Tie #'staff-position = #3.5
+    \once \override Tie.staff-position = #3.5
     bes1~ |
     \bar "||"
     \time 6/4
     bes2.^\markup { \bold "Moderato" } r8
     \mergeDifferentlyHeadedOn
     \mergeDifferentlyDottedOn
     % Start polyphonic section of four voices
     <<
       { c,8 d fis bes a }  % continuation of main voice
       \new Voice {
@@ skipping 49 matching lines @@
 @cindex NoteColumn, example of overriding
 @cindex force-hshift property, example
 @cindex Stem, example of overriding
 @cindex transparent property, example
 
 @c line-width ensures no break
 @lilypond[quote,verbatim,ragged-right,line-width=6\in]
 rhMusic = \relative c'' {
   \new Voice {
     r2 c4.\( g8 |
-    \once \override Tie #'staff-position = #3.5
+    \once \override Tie.staff-position = #3.5
     bes1~ |
     \bar "||"
     \time 6/4
     bes2.^\markup { \bold "Moderato" } r8
     \mergeDifferentlyHeadedOn
     \mergeDifferentlyDottedOn
     % Start polyphonic section of four voices
     <<
       { c,8 d fis bes a }  % continuation of main voice
       \new Voice {
         \voiceTwo
         c,8~
         % Reposition the c2 to the right of the merged note
-        \once \override NoteColumn #'force-hshift = #1.0
+        \once \override NoteColumn.force-hshift = #1.0
         % Move the c2 out of the main note column
         % so the merge will work
         \shiftOnn
         c2
       }
       \new Voice {
         \voiceThree
         s8
         % Stem on the d2 must be down to permit merging
         \stemDown
         % Stem on the d2 should be invisible
-        \tweak Stem #'transparent ##t
-        \tweak Flag #'transparent ##t
+        \tweak Stem.transparent ##t
+        \tweak Flag.transparent ##t
         d2
       }
       \new Voice {
         \voiceFour
         s4 fis4.
       }
     >> |
     \mergeDifferentlyHeadedOff
     \mergeDifferentlyDottedOff
     g2.\)  % continuation of main voice
@@ skipping 61 matching lines @@
 @noindent
 and blanking the first up-stem in that voice, the tie appears to
 cross voices:
 
 @cindex Stem, example of overriding
 @cindex transparent property, example
 
 @lilypond[quote,fragment,relative=2,verbatim]
 <<
   {
-    \tweak Stem #'transparent ##t
-    \tweak Flag #'transparent ##t
+    \tweak Stem.transparent ##t
+    \tweak Flag.transparent ##t
     b8~ b\noBeam
   }
 \\
   { b8[ g] }
 >>
 @end lilypond
 
 To make sure that the just-blanked stem doesn't squeeze the tie
 too much, we can lengthen the stem by setting the
 @code{length} to @code{8},
 
 @lilypond[quote,fragment,relative=2,verbatim]
 <<
   {
-    \tweak Stem #'transparent ##t
-    \tweak Flag #'transparent ##t
-    \tweak Stem #'length #8
+    \tweak Stem.transparent ##t
+    \tweak Flag.transparent ##t
+    \tweak Stem.length #8
     b8~ b\noBeam
   }
 \\
   { b8[ g] }
 >>
 @end lilypond
 
 @subheading Simulating a fermata in MIDI
 
 @cindex stencil property, use of
@@ skipping 17 matching lines @@
 
 @cindex MetronomeMark, example of overriding
 @cindex transparent property, example
 
 @lilypond[quote,verbatim,ragged-right]
 \score {
   \relative c'' {
     % Visible tempo marking
     \tempo 4=120
     a4 a a
-    \once \override Score.MetronomeMark #'transparent = ##t
+    \once \override Score.MetronomeMark.transparent = ##t
     % Invisible tempo marking to lengthen fermata in MIDI
     \tempo 4=80
     a4\fermata |
     % New tempo for next section
     \tempo 4=100
     a4 a a a |
   }
   \layout { }
   \midi { }
 }
 @end lilypond
 
 @cindex MetronomeMark, example of overriding
 @cindex stencil property, example
 
 @lilypond[quote,verbatim,ragged-right]
 \score {
   \relative c'' {
     % Visible tempo marking
     \tempo 4=120
     a4 a a
-    \once \override Score.MetronomeMark #'stencil = ##f
+    \once \override Score.MetronomeMark.stencil = ##f
     % Invisible tempo marking to lengthen fermata in MIDI
     \tempo 4=80
     a4\fermata |
     % New tempo for next section
     \tempo 4=100
     a4 a a a |
   }
   \layout { }
   \midi { }
 }
@@ skipping 23 matching lines @@
 
 Suppose we wish to emphasize certain words in lyrics by printing
 them in bold italics.  The @code{\italic} and @code{\bold}
 commands only work within lyrics if they are embedded, together with
 the word or words to be modified, within a @code{\markup} block,
 which makes them tedious to enter.  The need to embed the words
 themselves prevents their use in simple variables.  As an
 alternative can we use @code{\override} and @code{\revert} commands?
 
 @example
-@code{\override Lyrics . LyricText #'font-shape = #'italic}
-@code{\override Lyrics . LyricText #'font-series = #'bold}
-
-@code{\revert Lyrics . LyricText #'font-shape}
-@code{\revert Lyrics . LyricText #'font-series}
+@code{\override Lyrics.LyricText.font-shape = #'italic}
+@code{\override Lyrics.LyricText.font-series = #'bold}
+
+@code{\revert Lyrics.LyricText.font-shape}
+@code{\revert Lyrics.LyricText.font-series}
 @end example
 
 These would also be extremely tedious to enter if there were many
 words requiring emphasis.  But we @emph{can} define these as two
 variables and use those to bracket the words to be emphasized.
 Another advantage of using variables for these overrides is that
 the spaces around the dot are not necessary, since they are not
 being interpreted in @code{\lyricmode} directly.  Here's an example
 of this, although in practice  we would choose shorter names
 for the variables to make them quicker to type:
 
 @cindex LyricText, example of overriding
 @cindex font-shape property, example
 @cindex font-series property, example
 
 @lilypond[quote,verbatim]
 emphasize = {
-  \override Lyrics.LyricText #'font-shape = #'italic
-  \override Lyrics.LyricText #'font-series = #'bold
+  \override Lyrics.LyricText.font-shape = #'italic
+  \override Lyrics.LyricText.font-series = #'bold
 }
 
 normal = {
-  \revert Lyrics.LyricText #'font-shape
-  \revert Lyrics.LyricText #'font-series
+  \revert Lyrics.LyricText.font-shape
+  \revert Lyrics.LyricText.font-series
 }
 
 global = { \key c \major \time 4/4 \partial 4 }
 
 SopranoMusic = \relative c' { c4 | e4. e8 g4 g    | a4   a   g  }
 AltoMusic    = \relative c' { c4 | c4. c8 e4 e    | f4   f   e  }
 TenorMusic   = \relative c  { e4 | g4. g8 c4.  b8 | a8 b c d e4 }
 BassMusic    = \relative c  { c4 | c4. c8 c4 c    | f8 g a b c4 }
 
 VerseOne = \lyrics {
@@ skipping 163 matching lines @@
 
 inst =
 #(define-music-function
      (parser location string)
      (string?)
    #@{ ^\markup \bold \box #string #@})
 
 \layout@{
   \context @{
     \Score
-    \override MetronomeMark #'extra-offset = #'(-9 . 0)
-    \override MetronomeMark #'padding = #'3
+    \override MetronomeMark.extra-offset = #'(-9 . 0)
+    \override MetronomeMark.padding = #'3
   @}
   \context @{
     \Staff
-    \override TimeSignature #'style = #'numbered
+    \override TimeSignature.style = #'numbered
   @}
   \context @{
     \Voice
-    \override Glissando #'thickness = #3
-    \override Glissando #'gap = #0.1
+    \override Glissando.thickness = #3
+    \override Glissando.gap = #0.1
   @}
 @}
 @end example
 
 @lilypond[quote,ragged-right]
 mpdolce =
 #(make-dynamic-script
   #{ \markup { \hspace #0
                \translate #'(5 . 0)
                \line { \dynamic "mp"
                        \text \italic "dolce" } }
   #})
 
 inst =
 #(define-music-function
      (parser location string)
      (string?)
    #{ ^\markup \bold \box #string #})
 
 \layout{
   \context {
     \Score
-    \override MetronomeMark #'extra-offset = #'(-9 . 0)
-    \override MetronomeMark #'padding = #'3
+    \override MetronomeMark.extra-offset = #'(-9 . 0)
+    \override MetronomeMark.padding = #'3
   }
   \context {
     \Staff
-    \override TimeSignature #'style = #'numbered
+    \override TimeSignature.style = #'numbered
   }
   \context {
     \Voice
-    \override Glissando #'thickness = #3
-    \override Glissando #'gap = #0.1
+    \override Glissando.thickness = #3
+    \override Glissando.gap = #0.1
   }
 }
 
 \relative c'' {
   \tempo 4=50
   a4.\mpdolce d8 cis4--\glissando a |
   b4 bes a2 |
   \inst "Clarinet"
   cis4.\< d8 e4 fis |
   g8(\! fis)-. e( d)-. cis2 |
@@ skipping 22 matching lines @@
 #(define-music-function
      (parser location string)
      (string?)
    #@{ ^\markup \bold \box #string #@})
 
 #(set-global-staff-size 23)
 
 \layout@{
   \context @{
     \Score
-    \override MetronomeMark #'extra-offset = #'(-9 . 0)
-    \override MetronomeMark #'padding = #'3
+    \override MetronomeMark.extra-offset = #'(-9 . 0)
+    \override MetronomeMark.padding = #'3
   @}
   \context @{
     \Staff
   @}
   \context @{
     \Voice
-    \override Glissando #'thickness = #3
-    \override Glissando #'gap = #0.1
+    \override Glissando.thickness = #3
+    \override Glissando.gap = #0.1
   @}
 @}
 @end example
 
 @lilypond[quote,ragged-right]
 mpdolce =
 #(make-dynamic-script
   #{ \markup { \hspace #0
                \translate #'(5 . 0)
                \line { \dynamic "mp"
                        \text \italic "dolce" } }
   #})
 
 inst =
 #(define-music-function
      (parser location string)
      (string?)
    #{ ^\markup \bold \box #string #})
 
 #(set-global-staff-size 23)
 
 \layout{
   \context { \Score
-    \override MetronomeMark #'extra-offset = #'(-9 . 0)
-    \override MetronomeMark #'padding = #'3
+    \override MetronomeMark.extra-offset = #'(-9 . 0)
+    \override MetronomeMark.padding = #'3
   }
   \context { \Voice
-    \override Glissando #'thickness = #3
-    \override Glissando #'gap = #0.1
+    \override Glissando.thickness = #3
+    \override Glissando.gap = #0.1
   }
 }
 
 \relative c'' {
   \tempo 4=50
   a4.\mpdolce d8 cis4--\glissando a |
   b4 bes a2 |
   \inst "Clarinet"
   cis4.\< d8 e4 fis |
   g8(\! fis)-. e( d)-. cis2 |
@@ skipping 100 matching lines @@
 Open @file{ly/property-init.ly} in a text editor.  The one
 you normally use for @code{.ly} files will be fine.  This file
 contains the definitions of all the standard LilyPond predefined
 commands, such as @code{\stemUp} and @code{\slurDotted}.  You will
 see that these are nothing more than definitions of variables
 containing one or a group of @code{\override} commands.  For
 example, @code{/tieDotted} is defined to be:
 
 @example
 tieDotted = @{
-  \override Tie #'dash-period = #0.75
-  \override Tie #'dash-fraction = #0.1
+  \override Tie.dash-period = #0.75
+  \override Tie.dash-fraction = #0.1
 @}
 @end example
 
 If you do not like the default values these predefined commands can
 be redefined easily, just like any other variable, at the
 head of your input file.
 
 The following are the most useful files to be found in
 @file{ly/}:
 
@@ skipping 80 matching lines @@
        ((2) (x11-color 'orange ))  ; for D
        ((3) (x11-color 'yellow ))  ; for E
        ((4) (x11-color 'green  ))  ; for F
        ((5) (x11-color 'blue   ))  ; for G
        ((6) (x11-color 'purple ))  ; for A
        ((0) (x11-color 'violet ))  ; for B
        )))
 
 \relative c' {
   % Arrange to obtain color from color-notehead procedure
-  \override NoteHead #'color = #color-notehead
+  \override NoteHead.color = #color-notehead
   a2 b | c2 d | e2 f | g2 a |
 }
 @end lilypond
 
 Further examples showing the use of these programmable interfaces
 can be found in @rextend{Callback functions}.