Programming error

I am getting a programming error with the following code: %%% \version "2.24.3" % 2.25.14 too rightHand = \relative { c''4( c c c | \break g4 g \tuplet 3/2 4 { c,8) \change Staff = "lower" g[ g] } g4 | } \new PianoStaff << \new Staff = "upper" \righ

programming error in doc-snippet

Hi, with 2.25.0 /Documentation/snippets/new/ancient-notation-templatemodern-transcription-of-gregorian-music.ly emits: programming error: no stem for note column Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: \incipit sometimes returns programming error

On May 27, 2022, at 10:28, Jean Abou Samra wrote: > > Le 27/05/2022 à 14:34, Dan Eble a écrit : >> I would at least like to understand whether the error message is reasonable >> first. > > Do you mean whether it is reasonable for \bar "" during a >

Re: \incipit sometimes returns programming error

Le 27/05/2022 à 14:34, Dan Eble a écrit : I would at least like to understand whether the error message is reasonable first. Do you mean whether it is reasonable for \bar "" during a note to trigger a programming error, or whether it is reasonable for MensuralStaff to have "&q

Re: \incipit sometimes returns programming error

On May 26, 2022, at 11:36, Jean Abou Samra wrote: > I can't tell why the commit "Refactor BarLine engraving" had that > effect (and I'm not investigating). Dan, any thoughts? Should > MensuralStaff simply be changed to have measureBarType = ##f > (instead of "")? I think that measureBarType =

Re: \incipit sometimes returns programming error

ent = 5\cm incipit-width = 3\cm } } with recent versions it returns: programming error: Loose column does not have right side to attach to. First bad comit is: commit 8ae26d8330c603d249fec5953a887de9fbcbe31c Author: Dan Eble Date: Thu Mar 10 20:08:31 2022 -0500 Refactor BarLine

Re: \incipit sometimes returns programming error

;\layout { > > indent = 5\cm > > incipit-width = 3\cm > >} > > } > > > > with recent versions it returns: > > programming error: Loose column does not have right side to attach to. > > > > First bad comit is

Re: \incipit sometimes returns programming error

Le 26/05/2022 à 17:12, Thomas Morley a écrit : Hi, consider: \score { \new Staff \with { instrumentName = "" } { \incipit { c'1. } R1 } \layout { indent = 5\cm incipit-width = 3\cm } } with recent versions it returns: programming error: Loose column does not

\incipit sometimes returns programming error

Hi, consider: \score { \new Staff \with { instrumentName = "" } { \incipit { c'1. } R1 } \layout { indent = 5\cm incipit-width = 3\cm } } with recent versions it returns: programming error: Loose column does not have right side to attach to. First bad comit

Re: strict-note-spacing, grace, and spacer cause programming error

Le 22/03/2022 à 21:29, Knute Snortum a écrit : If you use strict-note-spacing (or strict-grace-spacing) with grace notes that contain a spacer, a programming error is encountered. Here is a MWE: %%% \version "2.23.6" \relative c { g4 \newSpacingSection

strict-note-spacing, grace, and spacer cause programming error

If you use strict-note-spacing (or strict-grace-spacing) with grace notes that contain a spacer, a programming error is encountered. Here is a MWE: %%% \version "2.23.6" \relative c { g4 \newSpacingSection \override Score.SpacingSpanner.strict-note-spacing = ##t \grace {

Re: compile message: programming error: no broken bound

`bug.ly' > Parsing... > Interpreting music... > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > programming error: no broken bound > continuing, cross fingers > programming error: no broken boun

compile message: programming error: no broken bound

Hi, When I compile this file, I get the following output: GNU LilyPond 2.19.83 Processing `bug.ly' Parsing... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... programming error: no broken bound continuing

Re: Strange "programming error: Loose column ..."

Am 27.12.19 um 00:33 schrieb Thomas Morley: Hi, the following code returns programming error: Loose column does not have right side to attach to. for all versions from 2.14.2 up to 2.21.0 No error for 2.12.3 { \set Score.defaultBarType = #"" r2 b1\glissando c' } You

Strange "programming error: Loose column ..."

Hi, the following code returns programming error: Loose column does not have right side to attach to. for all versions from 2.14.2 up to 2.21.0 No error for 2.12.3 { \set Score.defaultBarType = #"" r2 b1\glissando c' } Cheers, Harm _

Re: programming error/segfault while omitting Fingering.stencil with fingeringOrientations set 'left

> %% chord needs two elements to trigger the bug > } > > Versions 2.12.3 up to 2.16.2 print correctly, without error > > Versions 2.18.2 up to 2.19.82 print correctly, but return: > programming error: Infinity or NaN encountered > > Current master does: >

programming error/segfault while omitting Fingering.stencil with fingeringOrientations set 'left

: programming error: Infinity or NaN encountered Current master does: Segmentation fault (core dumped) Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Programming error when using very many grace notes [was: Re: ]

great product: 1. When using too many grace notes and you run the code it will give a message that says: “Programming error: going back in MIDI time” 1. Instrument names that are not very short get chopped 2. If a bar in a 4/4 rhythm piece has 64 note Sent from Mail<htt

Re: Crash: "programming error: trying to freeze time"

-- View this message in context: http://lilypond.1069038.n5.nabble.com/Crash-programming-error-trying-to-freeze-time-tp196555p196587.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gn

Re: Crash: "programming error: trying to freeze time"

Hello McLaren, in order to demonstrate good will, please apply the suggestions on code formatting and minimal examples I gave on the parallel post here as well; then I’ll act on the report. Best, Simon On 13.11.2016 07:14, mclaren wrote: also "programming error: trying to move bac

Crash: "programming error: trying to freeze time"

also "programming error: trying to move backward in time" also "programming error: Moment is not increasing. Aborting interpretation" \version "2.19.49" << % To get an interesting alternative bug, comment out the next line. Lilypond finishes, but only eng

Re: Simultaneous notes yield "programming error"

2016-09-02 9:59 GMT+02:00 Timothy Lanfear : > See the similar report by me to this list on 6 August and Harm's reply. > > Timothy Lanfear I've redone testing with Joel's file and a snapshot form latest master. No error or warning. Cheers, Harm

Re: Simultaneous notes yield "programming error"

Simon Albrecht writes: > Hi Joel, > > thanks for the report. > > On the user list, I may have exaggerated my zeal for minimal > examples. Here on the bug list, however, they are more strictly > required, so the bass clef and bar checks (which I believe are > certainly

Re: Simultaneous notes yield "programming error"

362im/programming_error.ly' >> Parsing... >> Interpreting music... >> Preprocessing graphical objects... >> Interpreting music... >> MIDI output to `programming_error.mid'... >> programming error: asked to compute volume at +1.00 for dynamic >> span o

Re: Simultaneous notes yield "programming error"

... Interpreting music... Preprocessing graphical objects... Interpreting music... MIDI output to `programming_error.mid'... programming error: asked to compute volume at +1.00 for dynamic span of duration 1.00 starting at 1 continuing, cross fingers programming error: asked to compute volume

Simultaneous notes yield "programming error"

... Preprocessing graphical objects... Interpreting music... MIDI output to `programming_error.mid'... programming error: asked to compute volume at +1.00 for dynamic span of duration 1.00 starting at 1 continuing, cross fingers programming error: asked to compute volume at +1.00 for dynamic span

Re: MIDI programming error with polyphony

2.19.46 > Processing `tmp.ly' > Parsing... > Interpreting music... > MIDI output to `tmp.midi'... > programming error: asked to compute volume at +0.25 for dynamic span of > duration 0.25 starting at 1/4 continuing, cross fingers > programming error: asked to compute v

MIDI programming error with polyphony

Bug first appears in 2.19.46. \version "2.19.46" \score { { a'4 << \new Voice a'4 \new Voice f'4 >> a'2 } \midi{} } generates GNU LilyPond 2.19.46 Processing `tmp.ly' Parsing... Interpreting music... MIDI output to `tmp.midi'... programming error: asked to compu

Vertical alignment - programming error

Using a grace note set that spans two staves, reduced from a vastly more complex real score to a more minimal example, if I use a hairpin between the sfz and the p indications, I get a programming error related to vertical alignment that I am unable to understand, or eliminate. Can folks

Re: Vertical alignment - programming error

simpler.ly < > http://exp-k-p11-simpler.ly/>]... > Processing `/home/andro/work/lilypond/proportion/exp-k-p11-simpler.ly < > http://exp-k-p11-simpler.ly/>' > Parsing... > Interpreting music... > Preprocessing graphical objects... > programming error: My pure_y_common

Re: Vertical alignment - programming error

On Mon, Oct 26, 2015 at 10:23 AM, David Nalesnik wrote: > > > A more minimal example triggers the warning with TimeSignature: > Two with TimeSignature, one with Clef. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Regression test 'arpeggio-no-staff-symbol.ly' generates a programming error

objects... programming error: vertical alignment called before line breaking continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `arpeggio-no-staff-symbol.ps'... Converting to `./arpeggio-no-staff-symbol.pdf'... Success

Regression test 'parenthesize-singlenotes-chords-rests.ly' generates a programming error

g r} \parenthesize| } --snip-- GNU LilyPond 2.19.3 Processing `parenthesize-singlenotes-chords-rests.ly' Parsing... Interpreting music... programming error: Don't know how to parenthesize spanners. continuing, cross fingers Preprocessing graphical objects... Finding the ideal number of pages

Regression test 'grace-end.ly' generates a programming error

the ideal number of pages... Fitting music on 1 page... Drawing systems... programming error: bounds of this piece aren't breakable. continuing, cross fingers Layout output to `grace-end.ps'... Converting to `./grace-end.pdf'... --snip-- http://code.google.com/p/lilypond/issues/detail?id=3850 James

Regression test 'grace-end-2.ly' generates a programming error

of pages... Fitting music on 1 page... Drawing systems... programming error: bounds of this piece aren't breakable. continuing, cross fingers Layout output to `grace-end-2.ps'... Converting to `./grace-end-2.pdf'... Success: compilation successfully completed --snip-- http://code.google.com/p/lilypond

Re: programming error with \markup \vspace used in \header

this message in context: http://lilypond.1069038.n5.nabble.com/programming-error-with-markup-vspace-used-in-header-tp158634p159064.html Sent from the Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org

Re: programming error with \markup \vspace used in \header

2014-02-04 Ralph Palmer ralphbugl...@gmail.com: On Thu, Jan 30, 2014 at 5:31 AM, Thomas Morley thomasmorle...@gmail.com wrote: Hi, the following code returns: programming error: Improbable offset for stencil: -inf staff space Setting to zero. although the printed output seems

Re: programming error with \markup \vspace used in \header

On Thu, Jan 30, 2014 at 5:31 AM, Thomas Morley thomasmorle...@gmail.comwrote: Hi, the following code returns: programming error: Improbable offset for stencil: -inf staff space Setting to zero. although the printed output seems to be correct. \version 2.19.1 \header { title

programming error with \markup \vspace used in \header

Hi, the following code returns: programming error: Improbable offset for stencil: -inf staff space Setting to zero. although the printed output seems to be correct. \version 2.19.1 \header { title = \markup \vspace #10 } \markup xy I noticed the error with 2.17.97, 2.18.0 and 2.19.1

programming error: cyclic dependency

Hello, the following minimal example seems to produce the correct result but lilypond raises a programming error: cyclic dependency: calculation-in-progress encountered for #'control-points (Slur). This might be related to Issue 2589. --Felix \version 2.16.0 \score { \new Staff

Re: programming error: cyclic dependency

Felix Janda wrote Hello, the following minimal example seems to produce the correct result but lilypond raises a programming error: cyclic dependency: calculation-in-progress encountered for #'control-points (Slur). This might be related to Issue 2589. sorry - I can't reproduce this! (I'm

Re: programming error: cyclic dependency

2013/6/25 Eluze elu...@gmail.com: Felix Janda wrote Hello, the following minimal example seems to produce the correct result but lilypond raises a programming error: cyclic dependency: calculation-in-progress encountered for #'control-points (Slur). This might be related to Issue 2589

Re: programming error: cyclic dependency

Thomas Morley thomasmorley65 at gmail.com writes: 2013/6/25 Eluze eluzew at gmail.com: but lilypond raises a programming error: cyclic dependency: calculation-in-progress encountered for #'control-points (Slur). This might be related to Issue 2589. sorry - I can't reproduce this! (I'm

Re: programming error: hyphen not finished yet

Hello, 2013/4/23 Benjamin Drung bdr...@debian.org I'm not top posting. Following small example causes Lilypond to spit out programming error: hyphen not finished yet [1]. Please either fix this bug or disallow the _ -- pattern for lyrics and print a useful error message. Thank you

programming error: hyphen not finished yet

I'm not top posting. Following small example causes Lilypond to spit out programming error: hyphen not finished yet [1]. Please either fix this bug or disallow the _ -- pattern for lyrics and print a useful error message. \version 2.16.0 sopranoLyrics = \lyricsto soprano { % correct: foo

Re: programming error while inserting ChordNames in Staff

Thomas Morley writes: 2013/3/30 Colin Hall colingh...@gmail.com Thomas, devs, what do you want to do with this thread? As David pointed out, it is expected behaviour now. Therefore I'd reject the bug report. OK, the bug report is duly rejected. Cheers, Colin. -- Colin Hall

Re: programming error while inserting ChordNames in Staff

on the German forum has tried this, for good reasons, and it failed with a programming error. David explained that this is not surprising. So, we can treat this as a bug, with a resolution that Lilypond detectings the condition and reports it as an error and exits. Or the feature of ChordNames within

Re: programming error while inserting ChordNames in Staff

2013/3/30 Colin Hall colingh...@gmail.com Thomas, devs, what do you want to do with this thread? As I understand it, a user on the German forum has tried this, for good reasons, and it failed with a programming error. David explained that this is not surprising. So, we can treat

programming error while inserting ChordNames in Staff

Hi, this code used to work with 2.16.2: \version 2.16.2 \new Staff \with { \accepts ChordNames } \new ChordNames \chordmode { \override ChordName #'Y-offset = #-1 c } With 2.17.12 an programming error occurs: GNU LilyPond 2.17.12 Processing `atest-22.ly' Parsing... Interpreting music

Re: programming error while inserting ChordNames in Staff

an programming error occurs: GNU LilyPond 2.17.12 Processing `atest-22.ly' Parsing... Interpreting music... programming error: duplicate axis group continuing, cross fingers Preprocessing graphical objects... programming error: vertical alignment called before line breaking continuing

Re: programming error while inserting ChordNames in Staff

2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants the ChordNames printed in a Staff. Is there a better way to achieve it? [...] I think if we

Re: programming error while inserting ChordNames in Staff

Thomas Morley thomasmorle...@googlemail.com writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants the ChordNames printed in a Staff. Is

Re: programming error while inserting ChordNames in Staff

2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants

Re: Issue 1412 in lilypond: programming error: Going back in MIDI time

Comment #3 on issue 1412 by plros...@gmail.com: programming error: Going back in MIDI time http://code.google.com/p/lilypond/issues/detail?id=1412 The same happens with \appoggiatura. It looks like Lilypond tries to borrow time from the previous note, but there is none. It may be OK

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Status: Verified Comment #17 on issue 2085 by colinpkc...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 Compiled input/regression/tablature-harmonic-functions.ly with 2.15.24

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: -Patch-countdown Patch-push Comment #14 on issue 2085 by colinpkc...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 Counted down to 20111219, please push

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Status: Fixed Labels: -Patch-push fixed_2_15_23 Comment #15 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 pushed as ab8c075..e8038c8 to staging

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Comment #11 on issue 2085 by d...@gnu.org: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 There are a number of cases in the manuals where stencils are just cleared out with ##f. That's reasonably

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Cc: adam.spi...@gmail.com Comment #12 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 Issue 2118 has been merged into this issue

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: Patch-review Comment #7 on issue 2085 by lilypond...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085#c7 Patchy the autobot says: LGTM

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: Patch-new Comment #8 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085#c8 Allow string numbers to have #f stencil without programming error (Issue

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: Patch-review Comment #9 on issue 2085 by lilypond...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085#c9 Patchy the autobot says: LGTM

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Comment #10 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 Another solution is to \override 'stencil to 'point-stencil instead of #f. This is described in the Learning

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: Patch-new Comment #5 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085#c5 Allow string numbers to have #f stencil without programming error (Issue

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Status: Started Owner: carl.d.s...@gmail.com Comment #6 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 (No comment was entered for this change

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Comment #3 on issue 2085 by d...@gnu.org: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 Since not being able to override the stencils to ##f (the obvious way to switch off string numbers) without warning leads

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Comment #4 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 I will try to get the simple fix done on Saturday. ___ bug-lilypond

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Comment #2 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 This is probably caused in New_fingering_engraver, in the position_scripts () function. To quote from the code

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Updates: Labels: Type-Ugly Comment #1 on issue 2085 by gra...@percival-music.ca: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 (No comment was entered for this change

Overriding stencil of StringNumber leads to programming error messages

objects... programming error: cannot align on self: empty element continuing, cross fingers programming error: cannot align on self: empty element continuing, cross fingers programming error: cannot align on self: empty element continuing, cross fingers programming error: cannot align on self: empty

Issue 2085 in lilypond: Overriding stencil of StringNumber leads to programming error messages

Status: Accepted Owner: New issue 2085 by idragos...@gmail.com: Overriding stencil of StringNumber leads to programming error messages http://code.google.com/p/lilypond/issues/detail?id=2085 the awful spacing of input/regression/tablature-harmonic-functions.ly let me to investigate

Re: programming error: no solution found for Bezier intersection

Am Wednesday, 14. September 2011, 06:47:50 schrieb Colin Campbell: On 11-09-13 09:29 PM, Nick Payne wrote: Ok, the following small example reproduces the error on my system with 2.15.11: The minimal example is (the normal fingering -1 does not have any influence, so it should be removed,

Re: programming error: no solution found for Bezier intersection

On 14/09/11 08:34, Trevor Daniels wrote: Nick Payne wrote Tuesday, September 13, 2011 11:25 PM The problem is that the score is quite large, and the log gives no indication at all about where the error is coming from. I guess I can try commenting out different sections to see if I can isolate

Re: programming error: no solution found for Bezier intersection

On 11-09-13 09:29 PM, Nick Payne wrote: Ok, the following small example reproduces the error on my system with 2.15.11: %== \version 2.15.11 \language english fingering = { \set fingeringOrientations = #'(left) \set strokeFingerOrientations =

Re: Issue 1492 in lilypond: page-count and programming error: number of pages is out of bounds

Updates: Labels: -Type-Other -Priority-Low Type-Defect Comment #1 on issue 1492 by percival.music.ca: page-count and programming error: number of pages is out of bounds http://code.google.com/p/lilypond/issues/detail?id=1492 (No comment was entered for this change

Re: Issue 1412 in lilypond: programming error: Going back in MIDI time

Comment #2 on issue 1412 by fiee.vis...@gmail.com: programming error: Going back in MIDI time http://code.google.com/p/lilypond/issues/detail?id=1412 Going back happens regularly with grace notes. ___ bug-lilypond mailing list bug-lilypond

Re: Issue 1412 in lilypond: programming error: Going back in MIDI time

lilyp...@googlecode.com writes: Comment #2 on issue 1412 by fiee.vis...@gmail.com: programming error: Going back in MIDI time http://code.google.com/p/lilypond/issues/detail?id=1412 Going back happens regularly with grace notes. I think that it would be nice to delay Midi output

Re: programming error: cannot align on self: empty element

Nick Payne nick.pa...@internode.on.net wrote in message news:4d9fdba1.9080...@internode.on.net... The following minimal example generates the error programming error: cannot align on self: empty element in the console log. \version 2.13.58 \relative c' { \tempo 4 = 72 \override

programming error: cannot align on self: empty element

The following minimal example generates the error programming error: cannot align on self: empty element in the console log. \version 2.13.58 \relative c' { \tempo 4 = 72 \override Score.MetronomeMark #'stencil = ##f c4 c c c } Comment out either the \tempo indication

Re: Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

Updates: Status: Verified Comment #4 on issue 1253 by brownian.box: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253 (No comment was entered for this change.) ___ bug

Issue 1492 in lilypond: page-count and programming error: number of pages is out of bounds

Status: Accepted Owner: Labels: Type-Other Priority-Low New issue 1492 by ralphbug...@gmail.com: page-count and programming error: number of pages is out of bounds http://code.google.com/p/lilypond/issues/detail?id=1492 2011/1/5 Nick Payne nick.pa...@internode.on.net: I have a score

Re: page-count and programming error: number of pages is out of bounds

pages. By adding page-count = 2 to the paper block it fits without any problem on two pages but the log then contains programming error: number of pages is out of bounds. With 2.13.45, this minimal example reproduces the error in the log. This example also gets warning: couldn't fit

Re: Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

Updates: Status: Fixed Labels: fixed_2_13_47 Comment #3 on issue 1253 by percival.music.ca: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253 Thanks, pushed. Attachments: 0001-Better-wording

Re: page-count and programming error: number of pages is out of bounds

but the log then contains programming error: number of pages is out of bounds. With 2.13.45, this minimal example reproduces the error in the log. This example also gets warning: couldn't fit music on page in the log, which doesn't happen with the actual score, where I only see the first error

Re: Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

Comment #1 on issue 1253 by markpolesky: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253 programming error: (de)crescendo on items with specified volume. Wouldn't it be enough simply to reword the error message? I

Re: Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

Updates: Labels: Patch Comment #2 on issue 1253 by percival.music.ca: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253 Patch looks ok to me, but let's make sure that we have the Patch label

Issue 1412 in lilypond: programming error: Going back in MIDI time

Status: Accepted Owner: Labels: Type-Other New issue 1412 by RalphBugList: programming error: Going back in MIDI time http://code.google.com/p/lilypond/issues/detail?id=1412 MIDIback.ly \version 2.13.35 music = \new Staff { \tempo 4 = 120 \time 2/4 \set Staff.midiInstrument

Re: programming error: Going back in MIDI time

On 18 Nov 2010, at 12:37, Ralph Palmer wrote: Thanks for your report. This has been accepted as Issue 1412 : http://code.google.com/p/lilypond/issues/detail?id=1412 Fine. Pondly (as Valentin would say), Pond-lily Yours, Hans ___

Issue 1253 in lilypond: programming error: (de)crescendo on items with specified volume.

Status: Accepted Owner: Labels: Type-Defect Priority-Medium Warning New issue 1253 by brownian.box: programming error: (de)crescendo on items with specified volume. http://code.google.com/p/lilypond/issues/detail?id=1253 http://lists.gnu.org/archive/html/lilypond-user/2010-09/msg00027

Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable.

Updates: Status: Verified Comment #4 on issue 1142 by brownian.box: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable. http://code.google.com/p/lilypond/issues/detail?id=1142 Great, thank You

Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable.

Status: Accepted Owner: New issue 1142 by brownian.box: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable. http://code.google.com/p/lilypond/issues/detail?id=1142 \version 2.13.25 \relative c'' { \repeat unfold 20 { c4 c c c

Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable.

Updates: Labels: Type-Defect Priority-Critical Regression Comment #1 on issue 1142 by brownian.box: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable. http://code.google.com/p/lilypond/issues/detail?id=1142 Sorry, labels

Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable.

Comment #2 on issue 1142 by brownian.box: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable. http://code.google.com/p/lilypond/issues/detail?id=1142 Sorry, i should mention: programming errors and exitcode = 1 and no output

Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable.

Updates: Status: Fixed Labels: fixed_2_13_26 Comment #3 on issue 1142 by joeneeman: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable. http://code.google.com/p/lilypond/issues/detail?id=1142 (No comment was entered for this change

Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces programming error

Status: Accepted Owner: New issue 1113 by brownian.box: score with Ambitus_engraver and voice with spacers only produces programming error http://code.google.com/p/lilypond/issues/detail?id=1113 Reported by David Kastrup: http://lists.gnu.org/archive/html/bug-lilypond/2010-06/msg00042

Re: What's the deal with this programming error?

Kastrup On Wed 09 Jun 2010, 17:02 Graham Percival wrote: On Wed, Jun 9, 2010 at 4:55 PM, James Bailey derhindem...@googlemail.com wrote: Am I to understand that a programming error should have a bug report? Yes; current policy is to record all warnings (even false warnings, which produce good

Re: Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces programming error

Updates: Labels: Type-Defect Priority-Low Warning Comment #1 on issue 1113 by brownian.box: score with Ambitus_engraver and voice with spacers only produces programming error http://code.google.com/p/lilypond/issues/detail?id=1113 (No comment was entered for this change

Re: Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces programming error

Comment #2 on issue 1113 by d...@gnu.org: score with Ambitus_engraver and voice with spacers only produces programming error http://code.google.com/p/lilypond/issues/detail?id=1113 Please note that the actual reported simplified test case throwing the error was \new Voice \with {\consists

Re: What's the deal with this programming error?

On Thu, Jun 10, 2010 at 3:23 PM, Graham Percival gra...@percival-music.ca wrote: Focus on processing other old reports that haven't been dealt with yet. I have (sorta) planned to do this as soon as I have a bit more time (several dozen hours are easily required), aka later this month. As for

Re: What's the deal with this programming error?

On Thu, Jun 10, 2010 at 03:32:46PM +0200, Valentin Villenave wrote: I have (sorta) planned to do this as soon as I have a bit more time (several dozen hours are easily required), aka later this month. If it takes you longer than 10 minutes to process a single email, you're doing something

  1   2   >