On Mon, Sep 06, 2010 at 10:57:36AM -0700, Paul Scott wrote: > On Mon, Sep 06, 2010 at 08:32:24AM +0000, lilyp...@googlecode.com wrote: > > Status: Accepted > > Owner: ---- > > Labels: Type-Defect Priority-Critical Regression > > > > New issue 1251 by brownian.box: StaffGroup with pauses and tempo > > indication causes segfault > > http://code.google.com/p/lilypond/issues/detail?id=1251 > > > > The segfault is triggered by the presence of the full-bar rest in > > here: http://codereview.appspot.com/2042043/ > > > > I'll apply the patch once I've sorted out a few additions for > > regression testing. > > > > While you're waiting for this to be fixed, you can use the following > > workaround: > > > > \once \override Score.MetronomeMark #'non-break-align-symbols = #'()
The above fixes the seg. fault. 2.13.32 Now I get mixed results with \tempo placement. (bug 684) Some start over the time signature and some start over the key signature. One of those placed over the key signature precedes the occurrance of the above workaround. Is this reasonable since 684 has been fixed? Thanks, Paul _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
