Wrong Type Argument 2.0

This started out a few days ago in lilypond-user, where I sent it not knowing if a bug was causing it or not. More tests indicate it probably is. --- Two-pass vertical spacing seems to be crashing with sufficiently large scores AND forcing line breaks. For example, the output below is pa

grace + partial autobeaming problem

It seems when a piece starts with a grace in a partial measure the autobeaming for the rest of the piece gets messed up. A work around is to add a spacer rest to the start. \version "2.11.18" \paper { ragged-right = ##t } \score { \new Staff \relative c' { \partial 8 \grace c16 c c c c

Re: Rehearsal mark appears on wrong staff

Trevor, could you take a look at this? If I remove the spacing weirdness, the rehearsal mark is created on the right staff. Do you know what's happening? Is this a good example for the bug tracker? Cheers, - Graham Daniel Johnson wrote: Sorry, the previous example should have been: %

Issue 287 in project lilypond

Issue 287: -dhelp doesn't work http://code.google.com/p/lilypond/issues/detail?id=287 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_19 -- You received this message because you are listed in the owner o

Issue 283 in project lilypond

Issue 283: bar numbers move vertically (and should not) http://code.google.com/p/lilypond/issues/detail?id=283 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_18 -- You received this message because you

Issue 288 in project lilypond

Issue 288: segfault, programming error bad number of pages http://code.google.com/p/lilypond/issues/detail?id=288 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_18 -- You received this message because y

Issue 280 in project lilypond

Issue 280: another x-staff cyclic issue http://code.google.com/p/lilypond/issues/detail?id=280 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_18 -- You received this message because you are listed in th

Re: Rehearsal mark appears on wrong staff

Sorry, the previous example should have been: % BEGIN \version "2.11.17" spaceWide = { \overrideProperty #"Score.NonMusicalPaperColumn" #'line-break-system-details #'((alignment-offsets . ( 0 -80 ))) } \score { << \new Staff { \spaceWide c''1 | \break \spaceWide c''1 | c''1 | \b

Rehearsal mark appears on wrong staff

When using absolute spacing and moving the Mark_engraver from the Score context to the Staff context (as described in section 8.1.4 of the Fine Manual), the mark is applied to the wrong staff. In the following example, the rehearsal mark should appear on the lower staff, but in the 2.11.17 version

Re: Issue 289 in project lilypond

[EMAIL PROTECTED] wrote: Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #2 by hanwenn: #74 Issue attribute updates: Status: Duplicate Are you sure? According to the original bug report behind #289, the problem does not exist

Issue 290 in project lilypond

Issue 290: ancient clef.scm file warning out of date http://code.google.com/p/lilypond/issues/detail?id=290 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_18 -- You received this message because you are

Issue 289 in project lilypond

Issue 289: grace note cancels \voiceOne http://code.google.com/p/lilypond/issues/detail?id=289 Comment #2 by hanwenn: #74 Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Re: Erratic Scores... Lilypond 2.11.16 / 2.11.17 Windows

On 2/12/07, Paul Scott <[EMAIL PROTECTED]> wrote: Trent Johnston wrote: > Hi Everyone, > > I don't know if anyone else has similar problems but 2.11.16 and > 2.11.17 with the automatic staff stretching I'm getting strange > results... most of my scores end up compiling with... > > warning: Can't

Convert-ly doesn't convert some ancient-font stuff

This is two bugs, but the file is pretty simple. If you really want two different files, I'll split it. Bug 1: Somewhere between 2.0 and 2.8, the clef names got hyphenated instead of having underscores. Convert-ly doesn't know about this, so a statement: \clef "petrucci_c1" should be

PianoStaff, multiple pages spacing issue

Hey, if you have a piano score that is bigger than one page, the music on all pages but the last is distributed over a page by extending the space between the two staffs of the PianoStaff instead of extending the space between the lines of the PianoStaff. There is a warning: "Warnung: Ca

simultaneous use of \( and \< yields avoid-slur warning

Moin, \version "2.11.17" \score { \relative{ c\<\( d\!\) } } gives this warning: " Warnung: Ignoring grob for slur: DynamicLineSpanner. avoid-slur not set? \relative{ c \<\( d\!\) }" ___ bug-lilypond mailing list bug-lilypond@

Re: barcheck fail when lyrics go across tied bar

Note also that you should use b2-> ~ | b4 instead of b2-> ( | b4) to get a tie (your current code gives a slur, which is something completely different). /Mats Graham Percival wrote: Arthur Lawrence wrote: %% words are correctly laid out but produce a barcheck failed message %% from bar 11