[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1103 in lilypond: Typo in engraver name while defining new contex
From: |
lilypond |
Subject: |
Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault |
Date: |
Thu, 27 May 2010 10:52:25 +0000 |
Status: Accepted
Owner: ----
Labels: Priority-Critical Type-Defect Regression
New issue 1103 by brownian.box: Typo in engraver name while defining new
contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
% ---------------------------------
\version "2.13.21"
% (stripped) example from
% http://lilypond.org/doc/v2.13/Documentation/a5/lily-1af976b8.ly :
\layout { \context {
\name ImproVoice
\type "Engraver_group"
\consists "Rhythmic_column_engraver_foo" % "typo" here
}
\context { \Staff
\accepts "ImproVoice"
}}
\relative c'' {
a4 d8 bes8 \new ImproVoice { c4^"ad lib" c
c4 c^"undress" c_"while playing :)" c }
a1
}
% ---------------------------------
2.12.3 compiles this successfully (with no "misspelled" engraver of course).
- Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault,
lilypond <=
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/27
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/28
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/28
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/30
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/30
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/30
- Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 2010/05/30