Hello Pat,
this is definitely a bug, I’d say. I’ll write to the bug list.
Two or three policy issues with this:
1. Don’t hijack existing threads, if your message has nothing at all to
do with their subject. Just compose a new message to the list – sorry,
but what’s so difficult about that?
2. (Re)read and follow <http://lilypond.org/tiny-examples.html>.
3. Code formatting: Generally, always surround {} and = and Scheme
expressions (those with `#') with spaces, even if they’re not
technically necessary. They make it easier to read.
Thank you,
Simon
On 29.12.2015 20:38, Patrick Karl wrote:
The following snippet contains three \score's, the third one commented
out:
%%% Begin snippet %%%
\version "2.19.32"
music = {
\tag #'noCues R1
\tag #'Cues {\cueDuring #"cueNotes" #DOWN R1 } % 1
d''8( e'' f'') r r2 % 2
}
cueNotes = \relative c'' {
s4. <g d'~>8 d' s4. % 1
}
\addQuote "cueNotes" \cueNotes
\score { \new Staff {\cueNotes } }
\score { \new Staff { \removeWithTag#'Cues \music } }
%\score { \new Staff { \keepWithTag#'Cues \music } }
%%% End snippet %%%
This snippet compiles ok, but if the third \score is uncommented, then
lilypond terminates with:
.
.
.
Preprocessing graphical objects...
Grob count 156
[lilypond_serif_3.068359375]
Interpreting music...Segmentation fault: 11
The problem appears to be the construct "<g d'~>8 d' " in the
cueNotes. Does anyone know why?
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user