Re: Manual volta repeat commands [was Re: Quoted text]

On 2008/05/31, Neil Puttock wrote: > The issue seems to be the lack of 'word-space: the function in > markup.scm, which is used by \line, is expecting a value for > 'word-space which doesn't exist, resulting in failure. Good catch! :-) > Markup which doesn't rely on 'word-space works fine, e.g \

Re: Manual volta repeat commands [was Re: Quoted text]

On Sat, 31 May 2008 00:26:50 +0100 "Neil Puttock" <[EMAIL PROTECTED]> wrote: > A simple fix would be to add a default for 'word-space to > VoltaBracket. Would anybody object if I push this fix (with an > input/new snippet for demonstration)? One general comment: - input/regression/ are for bug-f

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

Issue 629: input/regression/tie-accidental.ly http://code.google.com/p/lilypond/issues/detail?id=629 Comment #1 by n.puttock: (Apologies, I rather stupidly pressed return in the summary box before putting in a description.) This test is broken following commit 5ee50610e436e8dfd8cb7133b0341d26

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

Issue 629: input/regression/tie-accidental.ly http://code.google.com/p/lilypond/issues/detail?id=629 New issue report by n.puttock: We recommend that users report bugs to http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs Please DO NOT add issues directly to this tracker unless yo

Re: Manual volta repeat commands [was Re: Quoted text]

2008/5/30 John Mandereau <[EMAIL PROTECTED]>: > Maybe something like > > \set Score.repeatCommands = #(list (list 'volta (markup > #:line (#:simple "1.2.3..." #:roman (#:italic "ad lib." 'end-repeat) > > or an equivalent form > > voltaAdLib = \markup { "1.2.3..." \roman \italic "ad lib." } >

Re: appoggiatura at beginning fouls clef

2008/5/30 Graham Percival <[EMAIL PROTECTED]>: > I think this is another case of issue 34. :( Indeed. I added this as a comment. I definitely think this is no Enhancement, btw. Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http

Issue 34 in lilypond: Grace synchronization

Issue 34: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Comment #2 by v.villenave: % Another report from David: \version "2.11.47" \score { \context Staff << \clef "F" \relative c { \appoggiatura { c8[ d e] } f4 g a b } >> }

Re: appoggiatura at beginning fouls clef

On Fri, 30 May 2008 16:50:46 + David Bobroff <[EMAIL PROTECTED]> wrote: > The following example shows the problem. When the clef is given in > the score block as simultaneous with the predefined music the > appoggiatura causes the default clef (treble) to print before the > indicated clef (in

appoggiatura at beginning fouls clef

> I'm not top posting. I tried a search to see if this has been reported and did not find a report about this. The following example shows the problem. When the clef is given in the score block as simultaneous with the predefined music the appoggiatura causes the default clef (treble) to pr

Re: Issue 626 in lilypond: ottavation should accept markup

2008/5/30 <[EMAIL PROTECTED]>: > I added the regtest too late (after 2.11.47), but it's on Git master, so you > were > right to mark it as Verified despite your comment :-) What can I do, I'm just too confident :-) Cheers, Valentin ___ bug-lilypond

Issue 626 in lilypond: ottavation should accept markup

Issue 626: ottavation should accept markup http://code.google.com/p/lilypond/issues/detail?id=626 Comment #3 by john.mandereau: I added the regtest too late (after 2.11.47), but it's on Git master, so you were right to mark it as Verified despite your comment :-) -- You received this message

Manual volta repeat commands [was Re: Quoted text]

On 2008/05/29, Risto Vääräniemi wrote: > I noticed that the LP front page states that "LilyPond now allows all > text context properties to be markups". This does not yet cover volta > brackets, though. That is Score.repeatCommands, which only accepts > plain text. If you try to enter a markup the

Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

[EMAIL PROTECTED] wrote: Issue 628: Regression: markup \note doesn't work as a TimeSignature stencil http://code.google.com/p/lilypond/issues/detail?id=628 Comment #1 by hanwenn: without looking, I think the time sig does not work, because it uses the music font by default (to get the C symb

Issue 220 in lilypond: fingering too close to previous note

Issue 220: fingering too close to previous note http://code.google.com/p/lilypond/issues/detail?id=220 Comment #3 by hanwenn: this is actually tricky to solve: the alignment would have to depend on linespacing density, meaning that there have to be 2 positioning passes (one to determine minimum

Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

Issue 628: Regression: markup \note doesn't work as a TimeSignature stencil http://code.google.com/p/lilypond/issues/detail?id=628 Comment #1 by hanwenn: without looking, I think the time sig does not work, because it uses the music font by default (to get the C symbol). Should work if you add

Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby

Issue 625: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby http://code.google.com/p/lilypond/issues/detail?id=625 Comment #3 by hanwenn: another option is to let stencils have 2 extents. changing to enhancement. Issue attribute updates: Label

Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth

Issue 11: beamlet on wrong side of tuplet sixteenth http://code.google.com/p/lilypond/issues/detail?id=11 Comment #6 by hanwenn: Re defect vs. enhancement. - I use this field to prioritize fixes. Generally defects (we promised it would work) get attention more quickly, but require less work t

Issue 143 in lilypond: \setTextCresc incorrectly applied only once

Issue 143: \setTextCresc incorrectly applied only once http://code.google.com/p/lilypond/issues/detail?id=143 Comment #7 by reinhold.kainhofer: I don't think that \setTextDecrescOn make sense, because that's not an on/off setting, but one of many settings. In particular, for decrescendi we have -

Issue 143 in lilypond: \setTextCresc incorrectly applied only once

Issue 143: \setTextCresc incorrectly applied only once http://code.google.com/p/lilypond/issues/detail?id=143 Comment #6 by v.villenave: No, actually I was planning to raise the question on -devel again, following John's comment under Issue 566 :-) -- You received this message because you ar

Issue 143 in lilypond: \setTextCresc incorrectly applied only once

Issue 143: \setTextCresc incorrectly applied only once http://code.google.com/p/lilypond/issues/detail?id=143 Comment #5 by gpermus: By marking this Verified, you're almost guaranteeing that nobody will see it again. Does this mean you no longer think that we should rename the commands to \xxxO

Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround)

Issue 68: certain \paper variables put music at the bottom of the page (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=68 Comment #3 by gpermus: Then why does -padding work? Basically, -space is applied before the ragged-last is applied, whereas -padding is applied after.

Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil

Issue 628: Regression: markup \note doesn't work as a TimeSignature stencil http://code.google.com/p/lilypond/issues/detail?id=628 New issue report by v.villenave: % it works everywhere else, though. \version "2.11.47" % (also reproduced with 2.10) % was reported to work in 2.8 tsMarkup =\marku

Issue 245 in lilypond: partcombine multiple tuplet brackets false warning

Issue 245: partcombine multiple tuplet brackets false warning http://code.google.com/p/lilypond/issues/detail?id=245 Comment #1 by v.villenave: (Reproduced with 2.11.47) See also Issue 100. -- You received this message because you are listed in the owner or CC fields of this issue, or because

Issue 244 in lilypond: rests can be too high in polyphony if voiceTwo is low

Issue 244: rests can be too high in polyphony if voiceTwo is low http://code.google.com/p/lilypond/issues/detail?id=244 Comment #1 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Issue 239 in lilypond: words broken alternative ending don't get a hyphen

Issue 239: words broken alternative ending don't get a hyphen http://code.google.com/p/lilypond/issues/detail?id=239 Comment #4 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this iss

Issue 234 in lilypond: barcheck warning with multi-measure rest and \partial

Issue 234: barcheck warning with multi-measure rest and \partial http://code.google.com/p/lilypond/issues/detail?id=234 Comment #3 by v.villenave: (Reproduced with 2.11.47) I had never realized that Lily didn't report all the barchecks errors. Looks more like a feature than a bug, all we have to

Issue 220 in lilypond: fingering too close to previous note

Issue 220: fingering too close to previous note http://code.google.com/p/lilypond/issues/detail?id=220 Comment #2 by v.villenave: (Reproduced with 2.11.47) It took me a while to realize the fingering belonged to the last note :-) -- You received this message because you are listed in the own

Issue 218 in lilypond: center staccato over stem instead of notehead

Issue 218: center staccato over stem instead of notehead http://code.google.com/p/lilypond/issues/detail?id=218 Comment #1 by v.villenave: Yes indeed. Issue attribute updates: Labels: Engraving-nitpick -- You received this message because you are listed in the owner or CC fields of thi

Issue 217 in lilypond: articulation collides with beam

Issue 217: articulation collides with beam http://code.google.com/p/lilypond/issues/detail?id=217 Comment #5 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust

Issue 213 in lilypond: progerror \bendAfter

Issue 213: progerror \bendAfter http://code.google.com/p/lilypond/issues/detail?id=213 Comment #3 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue

Issue 202 in lilypond: merge-differently-headed should work for >2 voices

Issue 202: merge-differently-headed should work for >2 voices http://code.google.com/p/lilypond/issues/detail?id=202 Comment #7 by v.villenave: (Reproduced with 2.11.47) Carl, this kind of workaround could be added to the LSR now, tagged as "workaround". However, your code still produces some c

Issue 189 in lilypond: \episem over a single note

Issue 189: \episem over a single note http://code.google.com/p/lilypond/issues/detail?id=189 Comment #2 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your

Issue 187 in lilypond: Gregorian too much space between clef and first neume

Issue 187: Gregorian too much space between clef and first neume http://code.google.com/p/lilypond/issues/detail?id=187 Comment #1 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Issue 186 in lilypond: tenuto-accent looks ugly (accent too big)

Issue 186: tenuto-accent looks ugly (accent too big) http://code.google.com/p/lilypond/issues/detail?id=186 Comment #1 by v.villenave: (Reproduced with 2.11.47) I kinda like it this way though. Issue attribute updates: Labels: Engraving-nitpick -- You received this message because you

Issue 185 in lilypond: RhythmicStaff squishing chords should produce single notes

Issue 185: RhythmicStaff squishing chords should produce single notes http://code.google.com/p/lilypond/issues/detail?id=185 Comment #1 by v.villenave: (Reproduced with 2.11.47) Yes indeed. -- You received this message because you are listed in the owner or CC fields of this issue, or because

Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

Issue 163: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 Comment #6 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You

Issue 155 in lilypond: \parenthesize should take accidentals into account

Issue 155: \parenthesize should take accidentals into account http://code.google.com/p/lilypond/issues/detail?id=155 Comment #1 by v.villenave: (Reproduced with 2.11.47) Issue attribute updates: Summary: \parenthesize should take accidentals into account -- You received this message be

Issue 153 in lilypond: \once \set fails with MIDI instruments

Issue 153: \once \set fails with MIDI instruments http://code.google.com/p/lilypond/issues/detail?id=153 Comment #4 by v.villenave: (Reproduced with 2.11.47) The ability to change the instrument on the fly using \set is already a cool feature, if I may. -- You received this message because y

Issue 146 in lilypond: bar counters for normal bars

Issue 146: bar counters for normal bars http://code.google.com/p/lilypond/issues/detail?id=146 Comment #1 by v.villenave: Werner, could you add an example of your workaround to the LSR anyway? Thanks. -- You received this message because you are listed in the owner or CC fields of this issue,

Issue 141 in lilypond: harmonizing vertical tie positions

Issue 141: harmonizing vertical tie positions http://code.google.com/p/lilypond/issues/detail?id=141 Comment #3 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adju

Issue 139 in lilypond: tie misinterpreted as a slur

Issue 139: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 Comment #9 by v.villenave: (Still unfixed as of 2.11.47) Issue attribute updates: Status: Accepted Labels: -fixed_2_11_12 -- You received this message because you are listed in the ow

Issue 127 in lilypond: Dead contexts keep making an influence to the end of the line

Issue 127: Dead contexts keep making an influence to the end of the line http://code.google.com/p/lilypond/issues/detail?id=127 Comment #10 by v.villenave: (Reproduced in 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starre

Issue 110 in lilypond: floating columns need to look further back for rod distances in polyrhythmic cases

Issue 110: floating columns need to look further back for rod distances in polyrhythmic cases http://code.google.com/p/lilypond/issues/detail?id=110 Comment #11 by v.villenave: Seems to work as of 2.11.47. Issue attribute updates: Status: Verified -- You received this message because

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 #3 by v.villenave: Issue 17: \new Staff << \time 3/4 \partcombine \relative c'' { r8 e16\f( f) f g e e e e e e | \break r8 e16 f f g e e e e e e } \relative c''

Issue 99 in lilypond: lyric barline undefined behaviour

Issue 99: lyric barline undefined behaviour http://code.google.com/p/lilypond/issues/detail?id=99 Comment #3 by v.villenave: (Reproduced with 2.11.47) Issue attribute updates: Labels: Warning-nitpick -- You received this message because you are listed in the owner or CC fields of this

Issue 76 in lilypond: beam scoring should take accidentals into account

Issue 76: beam scoring should take accidentals into account http://code.google.com/p/lilypond/issues/detail?id=76 Comment #5 by v.villenave: (Reproduced in 2.11.47) The question is still unsolved. -- You received this message because you are listed in the owner or CC fields of this issue, or b

Issue 75 in lilypond: appogietta slur does not happen during normal slur

Issue 75: appogietta slur does not happen during normal slur http://code.google.com/p/lilypond/issues/detail?id=75 Comment #1 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue

Issue 69 in lilypond: automatically add mark to end of score request (easy workaround)

Issue 69: automatically add mark to end of score request (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=69 Comment #1 by v.villenave: (Reproduced with 2.11.47) This bug is documented in @knownissues, but it would be nice if it was addressed. -- You received this messag

Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround)

Issue 68: certain \paper variables put music at the bottom of the page (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=68 Comment #2 by v.villenave: (Reproduced with 2.11.47) Are we sure this is a bug? All LilyPond does is applying the required settings, isn't it? -- Yo

Issue 65 in lilypond: \accepts has problems with \with (lyrics should be between staves)

Issue 65: \accepts has problems with \with (lyrics should be between staves) http://code.google.com/p/lilypond/issues/detail?id=65 Comment #1 by v.villenave: (Reproduced with 2.11.47) The workaround is easy, but this is still an annoying limitation. Issue attribute updates: Labels: Usa

Issue 60 in lilypond: beam multiplicity changing on rests

Issue 60: beam multiplicity changing on rests http://code.google.com/p/lilypond/issues/detail?id=60 Comment #2 by v.villenave: (Reproduced with 2.11.47 -- even though I don't really understand the problem) -- You received this message because you are listed in the owner or CC fields of this is

Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby

Issue 625: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby http://code.google.com/p/lilypond/issues/detail?id=625 Comment #2 by joeneeman: This is a little tricky to solve. The problem is that the "edge" of the bracket is not counted towards that brack

Issue 59 in lilypond: rest collision engraver should take note durations into account.

Issue 59: rest collision engraver should take note durations into account. http://code.google.com/p/lilypond/issues/detail?id=59 Comment #3 by v.villenave: (Reproduced with 2.11.47) Issue attribute updates: Labels: Engraving-nitpick -- You received this message because you are listed i

Issue 54 in lilypond: clef moves multimeasure rest

Issue 54: clef moves multimeasure rest http://code.google.com/p/lilypond/issues/detail?id=54 Comment #4 by v.villenave: (Reproduced with 2.11.47) Indeed, a switch would be welcome. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starr

Issue 45 in lilypond: collision noteheads with four voices

Issue 45: collision noteheads with four voices http://code.google.com/p/lilypond/issues/detail?id=45 Comment #2 by v.villenave: (Reproduced with 2.11.47) I remember having seen such things in French contemporary scores -- though no real example comes to mind right now. -- You received this me

Issue 40 in lilypond: collision glissando accidental (includes workaround)

Issue 40: collision glissando accidental (includes workaround) http://code.google.com/p/lilypond/issues/detail?id=40 Comment #1 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this iss

Issue 39 in lilypond: collision flag notehead with polyphony

Issue 39: collision flag notehead with polyphony http://code.google.com/p/lilypond/issues/detail?id=39 Comment #1 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may ad

Issue 38 in lilypond: collision fingering beam

Issue 38: collision fingering beam http://code.google.com/p/lilypond/issues/detail?id=38 Comment #1 by v.villenave: (Reproduced with 2.11.47) It does only affect chords indeed. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred t

Issue 37 in lilypond: collision notehead and beams

Issue 37: collision notehead and beams http://code.google.com/p/lilypond/issues/detail?id=37 Comment #1 by v.villenave: (Reproduced with 2.11.47) Ugly! -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust

Issue 36 in lilypond: collision cresc and kneed beams

Issue 36: collision cresc and kneed beams http://code.google.com/p/lilypond/issues/detail?id=36 Comment #1 by v.villenave: (Reproduced with 2.11.47 -- it's even worse) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue

Issue 22 in lilypond: collision tuplet number and staff with increased spacing

Issue 22: collision tuplet number and staff with increased spacing http://code.google.com/p/lilypond/issues/detail?id=22 Comment #4 by v.villenave: (Reproduced with 2.11.47) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this

Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth

Issue 11: beamlet on wrong side of tuplet sixteenth http://code.google.com/p/lilypond/issues/detail?id=11 Comment #5 by v.villenave: (Reproduced with 2.11.47.) I agree with Comment 2 btw. -- You received this message because you are listed in the owner or CC fields of this issue, or because yo

Issue 143 in lilypond: \setTextCresc incorrectly applied only once

Issue 143: \setTextCresc incorrectly applied only once http://code.google.com/p/lilypond/issues/detail?id=143 Comment #4 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner

Issue 378 in lilypond: lyrics misplaced with Completion_heads_engraver

Issue 378: lyrics misplaced with Completion_heads_engraver http://code.google.com/p/lilypond/issues/detail?id=378 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the ow

Issue 434 in lilypond: unwanted direction change of broken tie

Issue 434: unwanted direction change of broken tie http://code.google.com/p/lilypond/issues/detail?id=434 Comment #2 by v.villenave: (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 440 in lilypond: Tie direction reverse incorrectly between whole notes tied across line breaks

Issue 440: Tie direction reverse incorrectly between whole notes tied across line breaks http://code.google.com/p/lilypond/issues/detail?id=440 Comment #5 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message b

Issue 455 in lilypond: wanted: vertical slur instead of arpeggio

Issue 455: wanted: vertical slur instead of arpeggio http://code.google.com/p/lilypond/issues/detail?id=455 Comment #2 by v.villenave: See also regtest "arpeggio-parenthesis.ly" -- very nice feature, if I may. Thanks Han-Wen! Issue attribute updates: Status: Verified -- You received t

Issue 463 in lilypond: switching on and off followVoice

Issue 463: switching on and off followVoice http://code.google.com/p/lilypond/issues/detail?id=463 Comment #2 by v.villenave: (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 field

Issue 488 in lilypond: flags take up space in other voice's tuplet

Issue 488: flags take up space in other voice's tuplet http://code.google.com/p/lilypond/issues/detail?id=488 Comment #3 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner

Issue 501 in lilypond: moving Bar_engraver into lyrics raises bar numbers

Issue 501: moving Bar_engraver into lyrics raises bar numbers http://code.google.com/p/lilypond/issues/detail?id=501 Comment #3 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the

Issue 521 in lilypond: \repeatTie direction depends on next note (?)

Issue 521: \repeatTie direction depends on next note (?) http://code.google.com/p/lilypond/issues/detail?id=521 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owne

Issue 615 in lilypond: lilypond-book 'relative' fragment option should imply 'fragment'

Issue 615: lilypond-book 'relative' fragment option should imply 'fragment' http://code.google.com/p/lilypond/issues/detail?id=615 Comment #1 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are

Issue 558 in lilypond: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break

Issue 558: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break http://code.google.com/p/lilypond/issues/detail?id=558 Comment #8 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message becau

Issue 568 in lilypond: converting ps to pdf looses output path dirname, plus patch to fix

Issue 568: converting ps to pdf looses output path dirname, plus patch to fix http://code.google.com/p/lilypond/issues/detail?id=568 Comment #3 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you

Issue 578 in lilypond: Regression: Completion heads mess up lyrics

Issue 578: Regression: Completion heads mess up lyrics http://code.google.com/p/lilypond/issues/detail?id=578 Comment #4 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner

Issue 585 in lilypond: Regression: Bass figures collapsing

Issue 585: Regression: Bass figures collapsing http://code.google.com/p/lilypond/issues/detail?id=585 Comment #4 by v.villenave: (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 fi

Issue 614 in lilypond: OttavaBracket left edge height not working

Issue 614: OttavaBracket left edge height not working http://code.google.com/p/lilypond/issues/detail?id=614 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner o

Issue 618 in lilypond: chords that include a 2nd can collide with other voices

Issue 618: chords that include a 2nd can collide with other voices http://code.google.com/p/lilypond/issues/detail?id=618 Comment #2 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed i

Issue 619 in lilypond: Regression: suggestAccidentals is broken

Issue 619: Regression: suggestAccidentals is broken http://code.google.com/p/lilypond/issues/detail?id=619 Comment #4 by v.villenave: (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 622 in lilypond: Rests cause cross-staff havoc

Issue 622: Rests cause cross-staff havoc http://code.google.com/p/lilypond/issues/detail?id=622 Comment #2 by v.villenave: Thanks Joe! Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you s

Issue 626 in lilypond: ottavation should accept markup

Issue 626: ottavation should accept markup http://code.google.com/p/lilypond/issues/detail?id=626 Comment #2 by v.villenave: I'll not mark it as verified until we have a regtest, though (otherwise it's likely to get forgotten). Issue attribute updates: Status: Verified -- You receive

Issue 480 in lilypond: collision: tie after line break with sharp/natural accidental

Issue 480: collision: tie after line break with sharp/natural accidental http://code.google.com/p/lilypond/issues/detail?id=480 Comment #1 by v.villenave: Reproduced with 2.11.47. See also Issue 55 where a similar collision was fixed (outside the staff). Issue attribute updates: Status

Issue 539 in lilypond: accidental missing in alternative

Issue 539: accidental missing in alternative http://code.google.com/p/lilypond/issues/detail?id=539 Comment #3 by v.villenave: ... And yet you forgot to mark it as "accepted" :-) Issue attribute updates: Status: Accepted -- You received this message because you are listed in the owner

Issue 582 in lilypond: slur and tie start in (almost) same spot

Issue 582: slur and tie start in (almost) same spot http://code.google.com/p/lilypond/issues/detail?id=582 Comment #1 by v.villenave: It looks the same with 2.11.47 (except that you have to specify ragged-right = ##f to see it happening). However, I'm not sure there has to be a better way (I r

Issue 593 in lilypond: extenders in FiguredBass add much vertical space

Issue 593: extenders in FiguredBass add much vertical space http://code.google.com/p/lilypond/issues/detail?id=593 Comment #1 by v.villenave: Yes indeed. Twice as much, to be precise. Issue attribute updates: Status: Accepted -- You received this message because you are listed in the o

Issue 594 in lilypond: end of repeat alternative consumes horizontal space

Issue 594: end of repeat alternative consumes horizontal space http://code.google.com/p/lilypond/issues/detail?id=594 Comment #1 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Accepted -- You received this message because you are listed in th

Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby

Issue 625: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby http://code.google.com/p/lilypond/issues/detail?id=625 Comment #1 by v.villenave: (No comment was entered for this change.) Issue attribute updates: Status: Accepted -- You received t