Re: error message problem

Graham Percival escreveu: Mike Dean wrote: C:/Program Files/LilyPond/usr/bin/../share/lilypond/current/ly/init.ly:41:1: error: GUILE signaled an error for the expression beginning here # (if (pair? toplevel-scores) C:/Program

Issue 277 in project lilypond

Issue 277: Bus error with page-break-permission + line-break-permission + ragged-right http://code.google.com/p/lilypond/issues/detail?id=277 Comment #5 by joeneeman: Never mind, it was easier than I thought. Issue attribute updates: Status: Fixed Labels: fixed_2_11_17 -- You

Re: Issue 277 in project lilypond

[EMAIL PROTECTED] wrote: Issue 277: Bus error with page-break-permission + line-break-permission + ragged-right http://code.google.com/p/lilypond/issues/detail?id=277 Comment #5 by joeneeman: Never mind, it was easier than I thought. Issue attribute updates: Status: Fixed

Re: Seg fault with 2.11.16

Paul Scott wrote: 2.11.16 gives the following error on code that worked on 2.11.15.2. This happens on both x86 and Mac OS X (Mac doesn't segfault but gives the same error message. I'm sorry I don't have enough time to give a short piece of code at the moment. I need to get some parts out

Re: Issue 277 in project lilypond

On 2/6/07, Paul Scott [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Issue 277: Bus error with page-break-permission + line-break-permission + ragged-right http://code.google.com/p/lilypond/issues/detail?id=277 Comment #5 by joeneeman: Never mind, it was easier than I thought. Issue

Re: Seg fault with 2.11.16

On 2/6/07, Paul Scott [EMAIL PROTECTED] wrote: Paul Scott wrote: 2.11.16 gives the following error on code that worked on 2.11.15.2. This happens on both x86 and Mac OS X (Mac doesn't segfault but gives the same error message. I'm sorry I don't have enough time to give a short piece of code

Re: Issue 277 in project lilypond

Joe Neeman wrote: On 2/6/07, Paul Scott [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Issue 277: Bus error with page-break-permission + line-break-permission + ragged-right http://code.google.com/p/lilypond/issues/detail?id=277 Comment #5 by joeneeman: Never mind, it was easier than

Re: Seg fault with 2.11.16

Joe Neeman wrote: On 2/6/07, Paul Scott [EMAIL PROTECTED] wrote: Paul Scott wrote: 2.11.16 gives the following error on code that worked on 2.11.15.2. This happens on both x86 and Mac OS X (Mac doesn't segfault but gives the same error message. I'm sorry I don't have enough time to give a

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #1 by [EMAIL PROTECTED]: A shorter example of cross-staff tuplet breakage: \version quot;2.11.16quot; \paper { ragged-right = ##t } \score { \new PianoStaff lt;lt; \new Staff =

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #2 by joeneeman: I have a partial fix in branch jneeman. It successfuly delays Tuplet_bracket::print until after line breaking, but the tuplet bracket is drawn wrong anyway (I added \override

Issue 282 in project lilypond

Issue 282: tuplet bracket printed over the wrong staff http://code.google.com/p/lilypond/issues/detail?id=282 New issue report by gpermus: % the tuplet bracket for the bottom staff is printed over the top staff, % but the tuplet number is printed correctly over the bottom staff. \version

Re: 2.11.15 debug help / detached beam

Ah, ok. I added the tuplet bracket problem as http://code.google.com/p/lilypond/issues/detail?id=282 Please only report one issue per email. For the --png thing, what operating system are you using? Cheers, - Graham Jay Anderson wrote: Hmm... I was using 2.11.15-1 on Fedora Core 6. With

Issue 282 in project lilypond

Issue 282: tuplet bracket printed over the wrong staff http://code.google.com/p/lilypond/issues/detail?id=282 Comment #1 by gpermus: Duplicate of issue 279, sorry. Issue attribute updates: Status: Duplicate -- You received this message because you are listed in the owner or CC fields

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #3 by hanwenn: .14 also fails this, and I suspect it was broken all along. The correct solution is to add stem-gt;relative_coordinate(common_y, Y_AXIS) to left amp; right Y coordinate.

Issue 283 in project lilypond

Issue 283: bar numbers move vertically (and should not) http://code.google.com/p/lilypond/issues/detail?id=283 New issue report by gpermus: % collision avoidance problem? The quot;2quot; bar number is way too high. \version quot;2.11.16quot; \relative c'' { c1 \break c''1 } Attachments: