t
higher.
Well I'm not a professionnal and i must admit it's the first time I read
this section. Hope it helps !
JMarc
Phil Burfitt a écrit :
Hello List,
Could anyone give me a detailed explanation of the following Stem
details...
beamed-minimum-free-lengths
beamed-extr
Hello List,
Could anyone give me a detailed explanation of the following Stem details...
beamed-minimum-free-lengths
beamed-extreme-minimum-free-lengths
The descriptions given in the Internals documentation don't make any sense
to me (probably my ignorance).
Thank you in advance.
On 22 April 2010 08:20, Rodolfo Zitellini wrote:
> Mmh interesting to debug! :)
Heh, I guess we're lucky it triggered a segfault as a side effect,
otherwise it could've gone unnoticed for even longer. :)
Here's the tracker entry:
http://code.google.com/p/lilypond/issues/detail?id=1063
As you c
On Wed, Apr 21, 2010 at 11:03 PM, Neil Puttock wrote:
>
> Nasty. :)
>
> Thanks for reporting this; I'll add it to the bug tracker once I've
> done a few more tests.
>
> It seems any override for Stem which precedes the nested override
> triggers the crash. Looks like there's a bug in the nested p
On 21 April 2010 15:20, Rodolfo Zitellini wrote:
> I get a segmentation fault (bus error). I am using MacOS X 10.5.8
> x86. Tried it with lilypond 2.12.1, 2.13.11, 2.13.18. It seems that
> the problem is generated by the \voiceOne (or \voiveTwo for the
> matter) - removing that it compiles fine.
Dear list,
Compiling the following snippet
notes = \relative c' {
\clef treble \key c \major \time 2/4
s16 [g s g ] s16 [g s g ] |
s16 [g s g ] \override Stem #'(details beamed-lengths) = #'(15 15)
s16 [g s g ] |
s16 [g s g ] s16 [g s g ] |
