[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1103 in lilypond: Typo in engraver name while defining new con
From: |
lilypond |
Subject: |
Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault |
Date: |
Sun, 30 May 2010 20:36:51 +0000 |
Comment #4 on issue 1103 by n.puttock: Typo in engraver name while defining
new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Thanks, that looks fine.
There's just one more thing, which I missed first time round:
This line,
SCM def = scm_call_1 (definition, cs);
needs emending to ensure scheme engravers defined as procedures are
initialized properly.
Thanks,
Neil
- 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/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 <=
- 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