Re: NEW: full measure rests fail to compress in compressMusic block

Hi Adam, Please construct a minimal example. Do you need all those \overrides? Do you need the manual beaming? The multiple staves? By "minimal", I mean "anything that can be gotten rid of, while still demonstrating the bug". There are more hints here: http://lilypond.org/web/devel/parti

NEW: full measure rests fail to compress in compressMusic block

> I'm not top posting. %% Full measure rests are not compressing along with music passed to the %% compressMusic function. Note that replacing "\time 3/8" with "\time 1/6" %% in the second staff of the example below sidesteps the problem. \version "2.11.33" \paper { ragged-rig

Re: full measure rests fail to compress in compressMusic block

Adam Wilson wrote: Explanation and code snippet at in the Lilypond Snippet Repository under "Printing full-measure rests inside a polymetric section using \compressMusic [0.5]:" http://lsr.dsi.unimi.it/LSR/Item?id=329 This is a nice idea for bug reports, but there are three problems: 1)

Issue 273 in lilypond: collision clef and note in strict proportional notation

Issue 273: collision clef and note in strict proportional notation http://code.google.com/p/lilypond/issues/detail?id=273 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 th

Issue 326 in lilypond: staff order for temporary staves

Issue 326: staff order for temporary staves http://code.google.com/p/lilypond/issues/detail?id=326 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

Issue 273 in lilypond: collision clef and note in strict proportional notation

Issue 273: collision clef and note in strict proportional notation http://code.google.com/p/lilypond/issues/detail?id=273 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 th

Issue 326 in lilypond: staff order for temporary staves

Issue 326: staff order for temporary staves http://code.google.com/p/lilypond/issues/detail?id=326 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

Issue 327 in lilypond: lyrics placement with two voice

Issue 327: lyrics placement with two voice http://code.google.com/p/lilypond/issues/detail?id=327 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

Issue 334 in lilypond: setting staff size not longer safe

Issue 334: setting staff size not longer safe http://code.google.com/p/lilypond/issues/detail?id=334 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Accepted -- You received this message because you are listed in the owner or CC fields

Re: accidentals.mirroredflat.backslash not working

Hi Andreas, I kind-of lost track of this bug. I just tested it with 2.11.33, and it certainly displays some output, but I don't know if it's correct or not. Could you test with the 2.11.33 binary and let me know if it's the wrong type of mirrorflat ? Cheers, - Graha, Andreas von Heydwolf

Issue 361 in lilypond: tremolo beams ignore fontSize

Issue 361: tremolo beams ignore fontSize http://code.google.com/p/lilypond/issues/detail?id=361 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 th

Issue 482 in lilypond: barline group changed in 2.11.33

Issue 482: barline group changed in 2.11.33 http://code.google.com/p/lilypond/issues/detail?id=482 New issue report by gpermus: %{ There should be no barline between the two staff groups; instead, this space in the bar line appears above the very last staff. There is a report that this worked in

Re: barline grouping changed between 11.32 and 11.33

Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=482 Cheers, - Graham Tapio Tuovila wrote: Hello, I'm typesetting a goncerto grosso -sort of score. Tried to group concertino and ripieni with 'system start delimiters'. Output is as hoped with .32 but different (not as hoped) w

Issue 364 in lilypond: TextSpanner #'bound-details #'left #'text can not suppress at start of line

Issue 364: TextSpanner #'bound-details #'left #'text can not suppress at start of line http://code.google.com/p/lilypond/issues/detail?id=364 Comment #2 by gpermus: Added to list of thing to do in GDP. Issue attribute updates: Status: Verified -- You received this message because you

Issue 416 in lilypond: removing Forbid_line_break_engraver doesn't always work

Issue 416: removing Forbid_line_break_engraver doesn't always work http://code.google.com/p/lilypond/issues/detail?id=416 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 th

Issue 82 in lilypond: partcombine incorrectly merges different rests

Issue 82: partcombine incorrectly merges different rests http://code.google.com/p/lilypond/issues/detail?id=82 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

Issue 17 in lilypond: partcombine doens't display rest

Issue 17: partcombine doens't display rest http://code.google.com/p/lilypond/issues/detail?id=17 Comment #5 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 t

Issue 466 in lilypond: CrossStaff uncompatible with crescendo

Issue 466: CrossStaff uncompatible with crescendo http://code.google.com/p/lilypond/issues/detail?id=466 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 fie

Issue 426 in lilypond: very short tie due to key signature

Issue 426: very short tie due to key signature http://code.google.com/p/lilypond/issues/detail?id=426 Comment #3 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

Issue 422 in lilypond: beamlets appear to touch

Issue 422: beamlets appear to touch http://code.google.com/p/lilypond/issues/detail?id=422 Comment #3 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 is

Issue 100 in lilypond: Partcombine must use note durations

Issue 100: Partcombine must use note durations http://code.google.com/p/lilypond/issues/detail?id=100 Comment #2 by gpermus: Specific bugs/requests in issues 17 and 82. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this iss

Issue 373 in lilypond: \repeat does not reset time signature (workaround included)

Issue 373: \repeat does not reset time signature (workaround included) http://code.google.com/p/lilypond/issues/detail?id=373 Comment #2 by gpermus: This was a dupe of 374. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC

Issue 465 in lilypond: Spacing collisision

Issue 465: Spacing collisision http://code.google.com/p/lilypond/issues/detail?id=465 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 371 in lilypond: \partial before \appoggiatura turns off beaming (workaround included)

Issue 371: \partial before \appoggiatura turns off beaming (workaround included) http://code.google.com/p/lilypond/issues/detail?id=371 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you

Issue 424 in lilypond: input/regression/accidental-forced-tie.ly

Issue 424: input/regression/accidental-forced-tie.ly http://code.google.com/p/lilypond/issues/detail?id=424 Comment #3 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

Issue 447 in lilypond: Unbeamed notes after a cadenza and an appogiatura

Issue 447: Unbeamed notes after a cadenza and an appogiatura http://code.google.com/p/lilypond/issues/detail?id=447 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 owne

Issue 335 in lilypond: extender passes beginning of second node

Issue 335: extender passes beginning of second node http://code.google.com/p/lilypond/issues/detail?id=335 Comment #3 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 f

Issue 265 in lilypond: accidental too close to left bar line (bar line padding problem?)

Issue 265: accidental too close to left bar line (bar line padding problem?) http://code.google.com/p/lilypond/issues/detail?id=265 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are

Issue 247 in lilypond: lyrics attached to Devnull are left-aligned instead of center-aligned

Issue 247: lyrics attached to Devnull are left-aligned instead of center-aligned http://code.google.com/p/lilypond/issues/detail?id=247 Comment #5 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you ar

Issue 421 in lilypond: beamlets appear to touch

Issue 421: beamlets appear to touch http://code.google.com/p/lilypond/issues/detail?id=421 Comment #1 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 is

Issue 459 in lilypond: Misaligned TrillSpanner across a line break

Issue 459: Misaligned TrillSpanner across a line break http://code.google.com/p/lilypond/issues/detail?id=459 Comment #4 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 C

Issue 457 in lilypond: general problem with \override and \once \override

Issue 457: general problem with \override and \once \override http://code.google.com/p/lilypond/issues/detail?id=457 Comment #6 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the own

Issue 420 in lilypond: trill spanner tr misaligned

Issue 420: trill spanner tr misaligned http://code.google.com/p/lilypond/issues/detail?id=420 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 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #:138:24: missing close paren

Issue 419: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #:138:24: missing close paren http://code.google.com/p/lilypond/issues/detail?id=419 Comment #12 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this messa

Issue 415 in lilypond: Hidden accidental of tied note still takes space

Issue 415: Hidden accidental of tied note still takes space http://code.google.com/p/lilypond/issues/detail?id=415 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

Issue 410 in lilypond: tie too short when clef change at end of system

Issue 410: tie too short when clef change at end of system http://code.google.com/p/lilypond/issues/detail?id=410 Comment #5 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

Issue 377 in lilypond: Ancient music template D.5.1 lost bar lines

Issue 377: Ancient music template D.5.1 lost bar lines http://code.google.com/p/lilypond/issues/detail?id=377 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

Issue 360 in lilypond: vertical spacing varies based on the first-page / not-first-page

Issue 360: vertical spacing varies based on the first-page / not-first-page http://code.google.com/p/lilypond/issues/detail?id=360 Comment #2 by gpermus: Agreed, this is fixed now. Issue attribute updates: Status: Verified -- You received this message because you are listed in the owne

Issue 323 in lilypond: right-oriented fingering fails to be oriented with slur

Issue 323: right-oriented fingering fails to be oriented with slur http://code.google.com/p/lilypond/issues/detail?id=323 Comment #3 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in th

Issue 294 in lilypond: absolute spacing moves Mark_engraver to wrong staff context

Issue 294: absolute spacing moves Mark_engraver to wrong staff context http://code.google.com/p/lilypond/issues/detail?id=294 Comment #2 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed i

Issue 242 in lilypond: note too close to left barline

Issue 242: note too close to left barline http://code.google.com/p/lilypond/issues/detail?id=242 Comment #5 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 t

Issue 216 in lilypond: staff line spacing not changed inside \layout{}

Issue 216: staff line spacing not changed inside \layout{} http://code.google.com/p/lilypond/issues/detail?id=216 Comment #3 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