Re: incorrect vertical spacing in pianostaff

On Thu, Oct 7, 2010 at 5:24 AM, Marten Visser wrote: > > Pertains at least to 2.13.32 and up. Lower versions not tested. > > between-staff-spacing #'padding should be relative to the actual staff size, > but it's relative to default staff size. > > Output for 2.13.35 is attached. > > -

Re: Autobeaming and cadenzas (was: bug-lilypond Digest, Vol 95, Issue 11)

On Wed, Oct 6, 2010 at 10:14 AM, Carl Sorensen wrote: > > I agree that a revert would be more appropriate.  However, a revert would > be very difficult to accomplish, because there is no easy way to save the > "original" value.  The value is only known in the translation stage as a > context prope

Issue 1304 in lilypond: Autobeam setting should be reverted to setting before cadenza

Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1304 by pnorcks: Autobeam setting should be reverted to setting before cadenza http://code.google.com/p/lilypond/issues/detail?id=1304 This is a followup issue to Issue 1289. Starting with version 2.13.36, autobeami

Re: Autobeaming and cadenzas (was: bug-lilypond Digest, Vol 95, Issue 11)

On Thu, Oct 7, 2010 at 5:12 PM, Patrick McCarty wrote: > On Wed, Oct 6, 2010 at 10:14 AM, Carl Sorensen wrote: >> >> On 10/5/10 11:44 PM, "David Kastrup" wrote: >>> >>> I think a revert would be more appropriate. >> >> I agree that a revert would be more appropriate.  However, a revert would >>

Re: Autobeaming and cadenzas (was: bug-lilypond Digest, Vol 95, Issue 11)

On Wed, Oct 6, 2010 at 10:14 AM, Carl Sorensen wrote: > > On 10/5/10 11:44 PM, "David Kastrup" wrote: > >> Carl Sorensen writes: >> >>> On 10/5/10 5:50 PM, "Keith E OHara" wrote: If \cadenzaOff turns autobeaming on, then what about scores that turn off autobeaming for the whole p

Re: Issue 1298 in lilypond: minimum-Y-extent must be updated manually

Comment #2 on issue 1298 by percival.music.ca: minimum-Y-extent must be updated manually http://code.google.com/p/lilypond/issues/detail?id=1298 Longer explanation: I want somebody to figure out what that property did (in 2.12), then figure out what the new command is called (in 2.13.36),

Re: Issue 1281 in lilypond: enhancement: lilypond-book safe mode

Comment #1 on issue 1281 by julien.rioux: enhancement: lilypond-book safe mode http://code.google.com/p/lilypond/issues/detail?id=1281 I'm providing a simple patch for this. Attachments: safe-mode.patch 1.4 KB ___ bug-lilypond mailing li

Re: Issue 1288 in lilypond: running convert-ly on git

Updates: Summary: running convert-ly on git Status: Started Owner: percival.music.ca Comment #1 on issue 1288 by percival.music.ca: running convert-ly on git http://code.google.com/p/lilypond/issues/detail?id=1288 In more general terms, we need to figure out when to run c

Re: Issue 1298 in lilypond: minimum-Y-extent must be updated manually

Comment #1 on issue 1298 by pkx1...@hotmail.com: minimum-Y-extent must be updated manually http://code.google.com/p/lilypond/issues/detail?id=1298 patch submitted to graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/ma

Re: Issue 1033 in lilypond: Documentation: \new Score must die

Comment #9 on issue 1033 by pkx1...@hotmail.com: Documentation: \new Score must die http://code.google.com/p/lilypond/issues/detail?id=1033 Hello, \new Score has been removed from all examples in the Doc now and any other references have either also been removed or adjusted to state that t

Re: Issue 1302 in lilypond: time engraved twice when starting with an acciaccatura

Updates: Status: Duplicate Mergedinto: 34 Comment #3 on issue 1302 by Carl.D.Sorensen: time engraved twice when starting with an acciaccatura http://code.google.com/p/lilypond/issues/detail?id=1302 Duplicate of 34. ___ bug-lilypond

Re: Issue 34 in lilypond: Grace synchronization

Comment #11 on issue 34 by Carl.D.Sorensen: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Issue 1302 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listin

Re: Issue 1297 in lilypond: Polyphonic TrillSpanners should be stacked accordingly to their Voice's position

Comment #3 on issue 1297 by v.villenave: Polyphonic TrillSpanners should be stacked accordingly to their Voice's position http://code.google.com/p/lilypond/issues/detail?id=1297 Paco, I'm opening issue 1303 re. your comment. ___ bug-lilypond maili

Issue 1303 in lilypond: Consecutive TrillSpanners may be chained or stacked, depending on the syntax.

Status: Accepted Owner: Labels: Type-Documentation Priority-Medium New issue 1303 by v.villenave: Consecutive TrillSpanners may be chained or stacked, depending on the syntax. http://code.google.com/p/lilypond/issues/detail?id=1303 As pointed out by Francisco as a comment in issue 1297,

Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t

Comment #9 on issue 405 by pkx1...@hotmail.com: tupletBracket not printed despite #'bracket-visibility=##t http://code.google.com/p/lilypond/issues/detail?id=405 No. As has been stated previously "LilyPond 2.12.3 released! December 20, 2009 We are happy to announce the release of LilyPond 2.

Re: Issue 1302 in lilypond: time engraved twice when starting with an acciaccatura

Comment #2 on issue 1302 by pkx1...@hotmail.com: time engraved twice when starting with an acciaccatura http://code.google.com/p/lilypond/issues/detail?id=1302 This one http://code.google.com/p/lilypond/issues/detail?id=34 ___ bug-lilypond mailing

Re: Issue 1300 in lilypond: Badly placed cross-staff beam, similar to Issue 506

Updates: Labels: Priority-Medium Comment #1 on issue 1300 by PhilEHolmes: Badly placed cross-staff beam, similar to Issue 506 http://code.google.com/p/lilypond/issues/detail?id=1300 (No comment was entered for this change.) ___ bug-lilypon

Re: Issue 1301 in lilypond: Strange collision of note and clef

Updates: Labels: Priority-High Comment #1 on issue 1301 by PhilEHolmes: Strange collision of note and clef http://code.google.com/p/lilypond/issues/detail?id=1301 Not a regression, but pretty ugly. ___ bug-lilypond mailing list bug-lilypond@g

Re: Issue 1302 in lilypond: time engraved twice when starting with an acciaccatura

Comment #1 on issue 1302 by wbsoft: time engraved twice when starting with an acciaccatura http://code.google.com/p/lilypond/issues/detail?id=1302 Isn't this a known issue (Notation, Rhythms, Special rhythmic concerns, Grace notes)? inserting \grace s8 in voiceA solves the problem. _