Re: DynamicTextSpanner is not fully contained in parent spanner

2010-09-10 Thread Jay Anderson
On Fri, Sep 10, 2010 at 12:52 AM, Urs Liska wrote: > Am 10.09.2010 06:33, schrieb Jay Anderson: >> >> \version "2.13.32" >> >> \score >> { >>   \new Staff \relative c' >>   { >>     %Works fine over break: >>     c1\cresc >>     \break >>     c1\f >> >>     \override DynamicTextSpanner #'style = #

Re: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen
This bug is now fixed, so there's no need to open an issue. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

close voices influence noteheads/ledger lines

2010-09-10 Thread Patrick Schmidt
Hi all, when voices get very close to one another ledger lines and/or note heads seem to change their behavior. In the following example the note head of the c is too far to the right. The ledger lines of the notes on the left side of the chord are shorter than normal. The ledger line of

Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4

2010-09-10 Thread lilypond
Updates: Status: Verified Comment #19 on issue 894 by percival.music.ca: lilypond-book fails from the command-line in OSX 10.4 http://code.google.com/p/lilypond/issues/detail?id=894 meh, I can't be bothered to wait for a proper verification. _

Re: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen
On 9/10/10 11:14 AM, "Graham Percival" wrote: > On Fri, Sep 10, 2010 at 11:10:05AM -0600, Carl Sorensen wrote: >> The message below shows a bug in the autobeaming code. >> >> Please mark is as a Defect with High priority (perhaps it should be >> Critical, rather than high, as it causes an int

Re: FW: Automatic beaming global settings

2010-09-10 Thread Graham Percival
On Fri, Sep 10, 2010 at 11:10:05AM -0600, Carl Sorensen wrote: > The message below shows a bug in the autobeaming code. > > Please mark is as a Defect with High priority (perhaps it should be > Critical, rather than high, as it causes an intended new feature not to > work). I believe that this fu

FW: Automatic beaming global settings

2010-09-10 Thread Carl Sorensen
The message below shows a bug in the autobeaming code. Please mark is as a Defect with High priority (perhaps it should be Critical, rather than high, as it causes an intended new feature not to work). Thanks, Carl -- Forwarded Message From: James Worlton Date: Fri, 10 Sep 2010 07:35:26 -0

Re: Tempo Segmentation Fault

2010-09-10 Thread Paul Scott
On Fri, Sep 10, 2010 at 07:32:59AM -0700, Jay Anderson wrote: > On Fri, Sep 10, 2010 at 1:07 AM, Phil Holmes wrote: > > Related to this? > > > > http://code.google.com/p/lilypond/issues/detail?id=1251 > > Yep, that's it. I guess I missed it in my searching. Thanks. Most important is workaround:

Re: Tempo Segmentation Fault

2010-09-10 Thread Jay Anderson
On Fri, Sep 10, 2010 at 1:07 AM, Phil Holmes wrote: > Related to this? > > http://code.google.com/p/lilypond/issues/detail?id=1251 Yep, that's it. I guess I missed it in my searching. Thanks. -Jay ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1260 in lilypond: Crash with \tempo

2010-09-10 Thread lilypond
Updates: Status: Invalid Comment #1 on issue 1260 by lilyli...@googlemail.com: Crash with \tempo http://code.google.com/p/lilypond/issues/detail?id=1260 Sorry, this is the same as issue #1251. I didn't find this one because I only searched for open issues (and 1251 is already fixed as

Re: Tempo Segmentation Fault

2010-09-10 Thread Urs Liska
Am 10.09.2010 07:29, schrieb Jay Anderson: \version "2.13.32" \score { << \new Staff { \tempo "Andante" 4=63 R1 } \new Staff { R1 } >> \layout { } } $ lilypond seg.ly GNU LilyPond 2.13.32 Processing `seg.ly' Parsing... Interpreti

Issue 1260 in lilypond: Crash with \tempo

2010-09-10 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical Regression New issue 1260 by lilyli...@googlemail.com: Crash with \tempo http://code.google.com/p/lilypond/issues/detail?id=1260 Reported by Jay Anderson: \version "2.13.32" \score { << \new Staff { %R1 % inserti

Re: Tempo Segmentation Fault

2010-09-10 Thread Phil Holmes
"Jay Anderson" wrote in message news:aanlkti==7jnywojnvnssd5xniocj5tbfa0cbkwrox...@mail.gmail.com... \version "2.13.32" \score { << \new Staff { \tempo "Andante" 4=63 R1 } \new Staff { R1 } >> \layout { } } $ lilypond seg.ly GNU LilyPond 2.13.32 Processi

Re: DynamicTextSpanner is not fully contained in parent spanner

2010-09-10 Thread Urs Liska
Am 10.09.2010 06:33, schrieb Jay Anderson: \version "2.13.32" \score { \new Staff \relative c' { %Works fine over break: c1\cresc \break c1\f \override DynamicTextSpanner #'style = #'none c1\cresc \break c1\f } } dts.ly:13:6: programming error:

Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break

2010-09-10 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1259 by lilyli...@googlemail.com: DynamicTextSpanner #'style = #'none doesn't work over \break http://code.google.com/p/lilypond/issues/detail?id=1259 \version "2.13.32" \score { \new Staff \relative c' { %Works

Issue 1258 in lilypond: Chord repetition with "q" gives error when used in tremolo

2010-09-10 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1258 by lilyli...@googlemail.com: Chord repetition with "q" gives error when used in tremolo http://code.google.com/p/lilypond/issues/detail?id=1258 \version "2.13.32" \new Staff \relative c' { %Causes error: 8 q q q

Re: Tremolo + Chord Repetition Error

2010-09-10 Thread Urs Liska
Am 10.09.2010 04:27, schrieb Jay Anderson: \version "2.13.32" \new Staff \relative c' { %Causes error: 8 q q q \repeat tremolo 4 q | %This works: %8 q q q \repeat tremolo 4 | } Hi Jay, I don't see why your first statement should be invalid. The docs say: "The chord repetitio