Peculiarities of identifier definitions

Can anybody explain to me what's going on in the following example: \version 2.11.12 myVoiceThree = #(context-spec-music (make-voice-props-set 2) 'Voice) \new Staff \new Voice {\voiceOne c' } \new Voice {\myVoiceThree e'} myFailingVoiceThree = { #(context-spec-music (make-voice-props-set 2)

Issue 243 in project lilypond

Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #2 by joeneeman: This is not actually what ragged-right does. What it does is to minimise the sum of quot;badnessquot; weights. I don't remember exactly what the weight is, but it depends on the

Issue 139 in project lilypond

Issue 139: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 Comment #8 by hanwenn: Actually, the fix got buried because it had other side-effects. I noticed this when trying to add NEWS entries. -- You received this message because you are listed in the

Re: Peculiarities of identifier definitions

Mats Bengtsson escreveu: Can anybody explain to me what's going on in the following example: \version 2.11.12 myVoiceThree = #(context-spec-music (make-voice-props-set 2) 'Voice) \new Staff \new Voice {\voiceOne c' } \new Voice {\myVoiceThree e'} myFailingVoiceThree = {

Issue 230 in project lilypond

Issue 230: segfault 2.11.10 http://code.google.com/p/lilypond/issues/detail?id=230 Comment #2 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_13 fixed_2_11_13 -- You received this message because you are listed in

Long StanzaNumber collides with the left vertical line connecting staves

Dear all, StanzaNumber precedes the lyrics, and extends to the left. If it becomes wide enough, it crosses the vertical line which connects the staves of a system (assuming a multi-staff system). Proper behaviour would probably be to shift the start of the notes and lyrics to the right, and

Issue 243 in project lilypond

Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #4 by joeneeman: Maybe I misunderstood the ragged-right stuff in Gourlay_breaker when I rewrote it. In any case, my previous comment wasn't quite correct -- the get the desired behaviour, it

Issue 243 in project lilypond

Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #5 by [EMAIL PROTECTED]: I don't really understand your comments Joe. Line breaking algorithms always handles the last word on the line specially, because you don't need to take the space after

error in init.ly? (lilypond 2.11.12)

Hello all-- I just downloaded LilyPond 2.11.12 GUB for Linux, convert-ly'ed one of my recent projects and ran LilyPond on the .ly file, and received this mysterious-looking (to me) error message-- --- begin quote of error message --- GNU LilyPond 2.11.12 Processing `blues-in-c-1.ly' Parsing...

Re: error in init.ly? (lilypond 2.11.12)

The file compiles fine with version 2.11.10 so there's something strange going on here. Normally, these kind of error messages indicate that you have a syntax error in your file, but since it works with 2.11.10, that seems unlikely. By commenting out sections of your file, I could narrow the

Issue 243 in project lilypond

Issue 243: really weird line breaks http://code.google.com/p/lilypond/issues/detail?id=243 Comment #6 by joeneeman: OK, if you don't want to maximise the shortest line then you can disregard my second point. The problem is this: when we space a justified line, we assign it a penalty based on

Re: error in init.ly? (lilypond 2.11.12)

Han-Wen Nienhuys wrote: Mats Bengtsson escreveu: The file compiles fine with version 2.11.10 so there's something strange going on here. Normally, these kind of error messages indicate that you have a syntax error in your file, but since it works with 2.11.10, that seems unlikely. By

Re: error in init.ly? (lilypond 2.11.12)

Mats Bengtsson escreveu: The file compiles fine with version 2.11.10 so there's something strange going on here. Normally, these kind of error messages indicate that you have a syntax error in your file, but since it works with 2.11.10, that seems unlikely. By commenting out sections of your

Re: Ragged-last likes to crowd last system

Rune Zedeler wrote: Rune Zedeler wrote: The following example should clearly typeset 20 bars on each system. In fact it typesets 13 on the first and 27 on the second. Is there a reason that this one didn't make it to the bug-tracker? For some reason I never got the email. I can see it in

MIDI file cuts off the last note

Hi! I just found that the MIDI file always cuts off the last note. In this example, it cuts off also a part of the note before. Is this bug has already been declared ? Frederic \version 2.11.12 \score { \new Staff { \set Staff.midiInstrument = #acoustic grand \time 4/4

Issue 87 in project lilypond

Issue 87: midi grace loses sync http://code.google.com/p/lilypond/issues/detail?id=87 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 issue,

Issue 245 in project lilypond

Issue 245: partcombine multiple tuplet brackets false warning http://code.google.com/p/lilypond/issues/detail?id=245 New issue report by gpermus: %%% false warning message foo.ly:10:8: warning: No tuplet to end \times 2/3 { b4 a g ~ } g2 [1] \version quot;2.11.12quot; \score

Issue 7 in project lilypond

Issue 7: \partcombine prints multiple tuplet brackets http://code.google.com/p/lilypond/issues/detail?id=7 Comment #6 by gpermus: OK, this bug is fixed; see #245 for the false warning. Issue attribute updates: Status: Verified -- You received this message because you are listed in the

Issue 246 in project lilypond

Issue 246: collision stanza number and system start http://code.google.com/p/lilypond/issues/detail?id=246 New issue report by gpermus: % Proper behaviour would probably be to shift the start of the % notes and lyrics % to the right, and space the starting matter (clef, % timesig, keysig)

Re: Long StanzaNumber collides with the left vertical line connecting staves

Thanks, this has been added as http://code.google.com/p/lilypond/issues/detail?id=246 Cheers, - Graham Sietse Brouwer wrote: Dear all, StanzaNumber precedes the lyrics, and extends to the left. If it becomes wide enough, it crosses the vertical line which connects the staves of a system

Issue 247 in project lilypond

Issue 247: lyrics attached to Devnull are left-aligned instead of center-aligned http://code.google.com/p/lilypond/issues/detail?id=247 New issue report by gpermus: Lyrics attached to a Voice are center-aligned if attached to a single note, and left-aligned if attached to a melisma. Lyrics

Re: Lyrics in Devnull context are left-aligned

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=247 I assume your earlier report about one of the Doc examples was the same issue. Cheers, - Graham Daniel Johnson wrote: Lyrics attached to a Voice are center-aligned if attached to a single note, and left-aligned if

Re: Tie bug

Hi On 1/18/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote: Can you run the test procedure ... and report whether it shows any unexpected problems? Ok, there a few (two or three) cases with chords that look worse. I'll have another look at the code in a few days. Erlend -- Han-Wen

Re: Bug: lyrics set to Devnull ignore implicit melismata

Thanks, this bug has been entered as http://code.google.com/p/lilypond/issues/detail?id=248 Thanks for the detailed explanation and multiple examples, but we find it easier to investigate the bug if we have a single, simple example -- see the bug tracker as an example of how much I compressed

Issue 135 in project lilypond

Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #2 by gpermus: I haven't seen a response to Mats' email (on Jan 3, 2007) on the subject, so I'm adding it here and marking the bug unresolved. Mats wrote: Can we turn this

Issue 240 in project lilypond

Issue 240: rest after \change Staff is placed below original materal on that staff http://code.google.com/p/lilypond/issues/detail?id=240 Comment #3 by gpermus: Sorry about the non-minimal example. Issue attribute updates: Status: Verified -- You received this message because you

Re: Ragged-last likes to crowd last system

Graham Percival skrev: I just tested it, and 2.11.12 places every note on the same line, Indeed, it does. I would call that a regression, it looks way too crowded. so I'm not certain if this report is still valid. It is. Just replace 40 with 42 and you will see the reported behaviour.

Issue 249 in project lilypond

Issue 249: ragged-right last line too crowded http://code.google.com/p/lilypond/issues/detail?id=249 New issue report by gpermus: \version quot;2.11.12quot; { \repeat unfold 42 c''1 } \paper { ragged-last = ##t indent = 0 } Attachments: foo.png 8.9 KB Issue attributes:

Re: MIDI file cuts off the last note

On Thu, Jan 18, 2007 at 05:51:37PM -0500, Frédéric Chiasson wrote: Hi! I just found that the MIDI file always cuts off the last note. In this example, it cuts off also a part of the note before. Is this bug has already been declared ? I've mentioned it, but the 2.11.11 (where it appeared)