Comment #3 on issue 1251 by v.villenave: StaffGroup with pauses and tempo
indication causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1251
Issue 1260 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu
Updates:
Status: Verified
Comment #2 on issue 1251 by v.villenave: StaffGroup with pauses and tempo
indication causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1251
Nice.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
On Mon, Sep 06, 2010 at 09:50:11PM +0100, Neil Puttock wrote:
> On 6 September 2010 20:03, Paul Scott wrote:
>
> > 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 si
Updates:
Status: Fixed
Owner: n.puttock
Labels: fixed_2_13_33
Comment #1 on issue 1251 by n.puttock: StaffGroup with pauses and tempo
indication causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1251
(No comment was entered for this change.)
On 6 September 2010 21:50, Neil Puttock wrote:
> On 6 September 2010 20:03, Paul Scott wrote:
>
>> 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 th
On Mon, Sep 06, 2010 at 10:57:36AM -0700, Paul Scott wrote:
> On Mon, Sep 06, 2010 at 08:32:24AM +, lilyp...@googlecode.com wrote:
> > Status: Accepted
> > Owner:
> > Labels: Type-Defect Priority-Critical Regression
> >
> > New issue 1251 by brownian.box: StaffGroup with pauses and tempo
On Mon, Sep 06, 2010 at 08:32:24AM +, 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/
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
Sorry, could not describe better.
This seems to be caught and "alm