Issue 275 in project lilypond

Issue 275: note-head-style.ly missing baroque and harmonic-black http://code.google.com/p/lilypond/issues/detail?id=275 Comment #5 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the

Issue 270 in project lilypond

Issue 270: bus error old scheme example piano spacing http://code.google.com/p/lilypond/issues/detail?id=270 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC

Issue 269 in project lilypond

Issue 269: bus error lyrics verses http://code.google.com/p/lilypond/issues/detail?id=269 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this iss

Issue 267 in project lilypond

Issue 267: \once fails for a glissando property http://code.google.com/p/lilypond/issues/detail?id=267 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC field

Issue 264 in project lilypond

Issue 264: url-link puts click area in wrong location http://code.google.com/p/lilypond/issues/detail?id=264 Comment #1 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or C

Issue 263 in project lilypond

Issue 263: false tupletSpannerDuration produces bracket until end of piece http://code.google.com/p/lilypond/issues/detail?id=263 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are list

Issue 259 in project lilypond

Issue 259: collision dynamic cresc http://code.google.com/p/lilypond/issues/detail?id=259 Comment #2 by gpermus: The cresc is still extremely close to the p; could the padding be increased? (the output from 2.10.0 still looks better, although IMO the 2.10.0 is a bit too big) File is from 2.10.0

Issue 253 in project lilypond

Issue 253: 2.11.13 bus error http://code.google.com/p/lilypond/issues/detail?id=253 Comment #12 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, o

Issue 175 in project lilypond

Issue 175: dashed line after \break too near to the staff http://code.google.com/p/lilypond/issues/detail?id=175 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner o

Issue 174 in project lilypond

Issue 174: text spanner must not contain shortened dashes http://code.google.com/p/lilypond/issues/detail?id=174 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner o

Issue 242 in project lilypond

Issue 242: note too close to left barline http://code.google.com/p/lilypond/issues/detail?id=242 Comment #1 by hanwenn: Looking into it, but it can worked around with average-spacing-wishes. -- You received this message because you are listed in the owner or CC fields of this issue, or because

Issue 284 in project lilypond

Issue 284: Segmentation fault -- tried to space systems on a bad number of pages http://code.google.com/p/lilypond/issues/detail?id=284 New issue report by trevorbaca: %%% BEGIN %%% \version "2.11.16" \new Score { \new Staff { \repeat unfold 16 { c'4 c'4 c'4 c'4 } } } %%% END %%% G

Re: \once \set Timing.defaultBarType fails!

Mats Bengtsson escreveu: > Why do the bar lines disappear completely in the following example? > > \version "2.11.15" > \relative{ > c1 | \once \set Timing.defaultBarType = ":" c1 | c1 | > } > > If you remove the \once, it works as expected and \once \set works > correctly > in other situations.

\once \set Timing.defaultBarType fails!

Why do the bar lines disappear completely in the following example? \version "2.11.15" \relative{ c1 | \once \set Timing.defaultBarType = ":" c1 | c1 | } If you remove the \once, it works as expected and \once \set works correctly in other situations. /Mats -- ==

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #4 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_17 -- You received this message because you are listed in t

Issue 271 in project lilypond

Issue 271: avoid-slur not set for dynamics and slur http://code.google.com/p/lilypond/issues/detail?id=271 Comment #1 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_17 -- You received this message because you ar

Re: Bug in line spanner code?

Cameron Horsburgh wrote: I've just looked at the 2.11 NEWS file and it seems there might be a bug in the new line spanner code. The glissando has completely disappeared, leaving only the arrow and mark up text. It's because of the ragged-right. I just remove it. Cheers, - Graham ___