Comment #10 on issue 1336 by percival.music.ca: skipTypesetting segfaults when set during a skipBars-induced MultiMeasureRest spanner
http://code.google.com/p/lilypond/issues/detail?id=1336
Other than my use of exit(0) and printf, that's the same as my patch in comment 3 on 1 Nov.
I'm not saying this to be snarky, or to object to this patch, but rather to highlight our inefficient use of resources. If this is an acceptable way to fix lilypond, and if we'd had a few more people discussing it, then this critical issue could have been closed almost a month ago.
As far as the patch goes, it looks fine to me -- but I'm notably ignorant about the internals and our general "architecture style".
_______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
