Well, on my system your snippet as you have written it throws no error
whatsoever... The result is exactly as I believe is the one you expected.
I rather suspect your way of organizing the lilypond file is creating
the error, or - perhaps more understandable - the fact that you are on a
mac
Grouping the key with the music is fine and gives no error (I’m using a Mac).
That’s reasonable since the key may change at places within the music.
JM
%%%
\version 2.19.15
music = \relative c'' {
\key c \major
e2 g,
\key e \minor
e2 g,
}
\score {
\new Staff
\music
The following snippet:
\version 2.19.15
music = \relative c'' { e2 g, }
\score {
\new Staff \key c \major \music
\layout {
\context { \Voice \consists Ambitus_engraver }
}
}
throws the following two programming errors:
* programming error: Note-column without
On Mon, Jan 12, 2015 at 05:25:55PM -0600, Cynthia Karl wrote:
The following snippet:
\version 2.19.15
music = \relative c'' { e2 g, }
\score{
\new Staff \key c \major \music
\layout {
\context { \Voice \consists Ambitus_engraver }
}
}
Your Staff line is
Cynthia Karl pckarl at mac.com writes:
\score{
\new Staff \key c \major \music
\layout {
\context { \Voice \consists Ambitus_engraver }
}
}
throws the following two programming errors:
Programming errors are intended to report conditions that a programmer
thinks
Cynthia Karl pckarl at mac.com writes:
IMO, the problem is that my simple snippet causes LilyPond to declare that
programing errors have occurred. Programming errors are a serious
problem. Programming errors are only
solved by correcting the program, not by avoiding them by modifying the
