Archives are refreshed every 30 minutes - for details, please visit the main index.
You can also download the archives in mbox format.

bug-lilypond (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Sat May 31 2008 17:13:47 -0400 Messages in reverse chronological order

[Next Period]

---

• May 31, 2008
  • Issue 541 in lilypond: Hebrew lyrics diacritic not well aligned, codesite-noreply, 17:13
  • Re: appoggiatura at beginning fouls clef, Mats Bengtsson, 14:40
  • Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil, Han-Wen Nienhuys, 10:47
  • Re: Manual volta repeat commands [was Re: Quoted text], John Mandereau, 02:34
• May 30, 2008
  • Re: Manual volta repeat commands [was Re: Quoted text], Graham Percival, 20:19
  • Issue 629 in lilypond: input/regression/tie-accidental.ly, codesite-noreply, 19:44
  • Issue 629 in lilypond: input/regression/tie-accidental.ly, codesite-noreply, 19:34
  • Re: Manual volta repeat commands [was Re: Quoted text], Neil Puttock, 19:26
  • Re: appoggiatura at beginning fouls clef, Valentin Villenave, 17:40
  • Issue 34 in lilypond: Grace synchronization, codesite-noreply, 17:40
  • Re: appoggiatura at beginning fouls clef, Graham Percival, 17:00
  • appoggiatura at beginning fouls clef, David Bobroff, 12:51
  • Re: Issue 626 in lilypond: ottavation should accept markup, Valentin Villenave, 12:33
  • Issue 626 in lilypond: ottavation should accept markup, codesite-noreply, 12:28
  • Manual volta repeat commands [was Re: Quoted text], John Mandereau, 12:17
  • Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil, Mats Bengtsson, 11:59
  • Issue 220 in lilypond: fingering too close to previous note, codesite-noreply, 10:26
  • Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil, codesite-noreply, 10:22
  • Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby, codesite-noreply, 10:18
  • Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth, codesite-noreply, 10:14
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 10:00
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 09:15
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 08:40
  • Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround), codesite-noreply, 08:36
  • Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil, codesite-noreply, 08:32
  • Issue 245 in lilypond: partcombine multiple tuplet brackets false warning, codesite-noreply, 08:28
  • Issue 244 in lilypond: rests can be too high in polyphony if voiceTwo is low, codesite-noreply, 08:24
  • Issue 239 in lilypond: words broken alternative ending don't get a hyphen, codesite-noreply, 08:20
  • Issue 234 in lilypond: barcheck warning with multi-measure rest and \partial, codesite-noreply, 08:16
  • Issue 220 in lilypond: fingering too close to previous note, codesite-noreply, 08:12
  • Issue 218 in lilypond: center staccato over stem instead of notehead, codesite-noreply, 08:08
  • Issue 217 in lilypond: articulation collides with beam, codesite-noreply, 08:04
  • Issue 213 in lilypond: progerror \bendAfter, codesite-noreply, 08:00
  • Issue 202 in lilypond: merge-differently-headed should work for >2 voices, codesite-noreply, 07:56
  • Issue 189 in lilypond: \episem over a single note, codesite-noreply, 07:52
  • Issue 187 in lilypond: Gregorian too much space between clef and first neume, codesite-noreply, 07:48
  • Issue 186 in lilypond: tenuto-accent looks ugly (accent too big), codesite-noreply, 07:44
  • Issue 185 in lilypond: RhythmicStaff squishing chords should produce single notes, codesite-noreply, 07:40
  • Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), codesite-noreply, 07:36
  • Issue 155 in lilypond: \parenthesize should take accidentals into account, codesite-noreply, 07:32
  • Issue 153 in lilypond: \once \set fails with MIDI instruments, codesite-noreply, 07:28
  • Issue 146 in lilypond: bar counters for normal bars, codesite-noreply, 07:24
  • Issue 141 in lilypond: harmonizing vertical tie positions, codesite-noreply, 07:20
  • Issue 139 in lilypond: tie misinterpreted as a slur, codesite-noreply, 07:16
  • Issue 127 in lilypond: Dead contexts keep making an influence to the end of the line, codesite-noreply, 07:12
  • Issue 110 in lilypond: floating columns need to look further back for rod distances in polyrhythmic cases, codesite-noreply, 07:08
  • Issue 100 in lilypond: Partcombine must use note durations, codesite-noreply, 07:04
  • Issue 99 in lilypond: lyric barline undefined behaviour, codesite-noreply, 07:00
  • Issue 76 in lilypond: beam scoring should take accidentals into account, codesite-noreply, 06:56
  • Issue 75 in lilypond: appogietta slur does not happen during normal slur, codesite-noreply, 06:52
  • Issue 69 in lilypond: automatically add mark to end of score request (easy workaround), codesite-noreply, 06:48
  • Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround), codesite-noreply, 06:44
  • Issue 65 in lilypond: \accepts has problems with \with (lyrics should be between staves), codesite-noreply, 06:40
  • Issue 60 in lilypond: beam multiplicity changing on rests, codesite-noreply, 06:36
  • Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby, codesite-noreply, 06:32
  • Issue 59 in lilypond: rest collision engraver should take note durations into account., codesite-noreply, 06:28
  • Issue 54 in lilypond: clef moves multimeasure rest, codesite-noreply, 06:24
  • Issue 45 in lilypond: collision noteheads with four voices, codesite-noreply, 06:20
  • Issue 40 in lilypond: collision glissando accidental (includes workaround), codesite-noreply, 06:16
  • Issue 39 in lilypond: collision flag notehead with polyphony, codesite-noreply, 06:12
  • Issue 38 in lilypond: collision fingering beam, codesite-noreply, 06:08
  • Issue 37 in lilypond: collision notehead and beams, codesite-noreply, 06:04
  • Issue 36 in lilypond: collision cresc and kneed beams, codesite-noreply, 06:00
  • Issue 22 in lilypond: collision tuplet number and staff with increased spacing, codesite-noreply, 05:56
  • Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth, codesite-noreply, 05:52
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 05:48
  • Issue 378 in lilypond: lyrics misplaced with Completion_heads_engraver, codesite-noreply, 05:44
  • Issue 434 in lilypond: unwanted direction change of broken tie, codesite-noreply, 05:40
  • Issue 440 in lilypond: Tie direction reverse incorrectly between whole notes tied across line breaks, codesite-noreply, 05:36
  • Issue 455 in lilypond: wanted: vertical slur instead of arpeggio, codesite-noreply, 05:32
  • Issue 463 in lilypond: switching on and off followVoice, codesite-noreply, 05:28
  • Issue 488 in lilypond: flags take up space in other voice's tuplet, codesite-noreply, 05:24
  • Issue 501 in lilypond: moving Bar_engraver into lyrics raises bar numbers, codesite-noreply, 05:20
  • Issue 521 in lilypond: \repeatTie direction depends on next note (?), codesite-noreply, 05:16
  • Issue 615 in lilypond: lilypond-book 'relative' fragment option should imply 'fragment', codesite-noreply, 05:12
  • Issue 558 in lilypond: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break, codesite-noreply, 05:08
  • Issue 568 in lilypond: converting ps to pdf looses output path dirname, plus patch to fix, codesite-noreply, 05:04
  • Issue 578 in lilypond: Regression: Completion heads mess up lyrics, codesite-noreply, 05:00
  • Issue 585 in lilypond: Regression: Bass figures collapsing, codesite-noreply, 04:56
  • Issue 614 in lilypond: OttavaBracket left edge height not working, codesite-noreply, 04:52
  • Issue 618 in lilypond: chords that include a 2nd can collide with other voices, codesite-noreply, 04:48
  • Issue 619 in lilypond: Regression: suggestAccidentals is broken, codesite-noreply, 04:44
  • Issue 622 in lilypond: Rests cause cross-staff havoc, codesite-noreply, 04:40
  • Issue 626 in lilypond: ottavation should accept markup, codesite-noreply, 04:36
  • Issue 480 in lilypond: collision: tie after line break with sharp/natural accidental, codesite-noreply, 04:32
  • Issue 539 in lilypond: accidental missing in alternative, codesite-noreply, 04:28
  • Issue 582 in lilypond: slur and tie start in (almost) same spot, codesite-noreply, 04:24
  • Issue 593 in lilypond: extenders in FiguredBass add much vertical space, codesite-noreply, 04:20
  • Issue 594 in lilypond: end of repeat alternative consumes horizontal space, codesite-noreply, 04:15
  • Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby, codesite-noreply, 04:12
• May 29, 2008
  • Re: Quoted text (was Re: When is "-" required in articulations?), Neil Puttock, 18:59
  • Issue 268 in lilypond: lilypond -dpreview crops too much, codesite-noreply, 16:25
  • Issue 268 in lilypond: lilypond -dpreview crops too much, codesite-noreply, 16:19
  • Re: Quoted text (was Re: When is "-" required in articulations?), Risto Vääräniemi, 09:31
  • Re: regressions 2.11.46-1; spacing-packed.ly, Graham Percival, 00:32
  • Re: regressions 2.11.46-1; lyrics-no-notes.ly, Graham Percival, 00:32
• May 28, 2008
  • Issue 334 in lilypond: setting staff size not longer safe, codesite-noreply, 22:59
  • Issue 334 in lilypond: setting staff size not longer safe, codesite-noreply, 22:55
  • Issue 268 in lilypond: lilypond -dpreview crops too much, codesite-noreply, 22:51
  • grace note makes voiceOne go stems down, Steven McDougall, 22:43
  • Re: regressions 2.11.46-1; option-help.ly, Han-Wen Nienhuys, 22:13
  • Re: regressions 2.11.46-1; spacing-packed.ly, Han-Wen Nienhuys, 22:12
  • Re: regressions 2.11.46-1; music-function.ly, Han-Wen Nienhuys, 22:11
  • Re: regressions 2.11.46-1; lyrics-no-notes.ly, Han-Wen Nienhuys, 22:09
  • Re: regressions 2.11.46-1; script-center-seconds.ly, Han-Wen Nienhuys, 22:07
  • Re: regressions 2.11.46-1; spacing-section.ly, Graham Percival, 19:36
  • Re: regressions 2.11.46-1; spacing-packed.ly, Graham Percival, 19:36
  • Re: regressions 2.11.46-1; spacing-accidental-tie.ly, Graham Percival, 19:36
  • Re: regressions 2.11.46-1; part-combine-text.ly, Graham Percival, 19:36
  • Re: regressions 2.11.46-1; music-function.ly, Graham Percival, 19:35
  • Re: regressions 2.11.46-1; lyrics-no-notes.ly, Graham Percival, 19:35
  • Re: regressions 2.11.46-1; chord-name-entry.ly, Graham Percival, 19:35
  • Issue 627 in lilypond: \compressMusic should be renamed to \scaleDurations, codesite-noreply, 17:09
  • Issue 541 in lilypond: Hebrew lyrics diacritic not well aligned, codesite-noreply, 15:02
  • regressions 2.11.46-1; spacing-section.ly, Stan Sanderson, 12:46
  • regressions 2.11.46-1; spacing-packed.ly, Stan Sanderson, 12:40
  • regressions 2.11.46-1; spacing-accidental-tie.ly, Stan Sanderson, 12:37
  • regressions 2.11.46-1; script-center-seconds.ly, Stan Sanderson, 12:35
  • regressions 2.11.46-1; part-combine-text.ly, Stan Sanderson, 12:30
  • regressions 2.11.46-1; option-help.ly, Stan Sanderson, 12:29
  • regressions 2.11.46-1; music-function.ly, Stan Sanderson, 12:27
  • regressions 2.11.46-1; lyrics-no-notes.ly, Stan Sanderson, 12:26
  • regressions 2.11.46-1; chord-name-entry.ly, Stan Sanderson, 12:13
  • Issue 566 in lilypond: showStaffSwitch -> \staffSwitchOn, codesite-noreply, 10:41
  • Issue 413 in lilypond: PNG image is offset an therefore cropped a little, codesite-noreply, 09:58
  • Issue 596 in lilypond: collision tuplet number and slur, codesite-noreply, 09:54
  • Issue 535 in lilypond: ly:stem::pure-height (expecting real number), codesite-noreply, 09:50
  • Issue 606 in lilypond: Completion_heads_engraver not working correctly, codesite-noreply, 09:44
  • Issue 486 in lilypond: chord fonts in OSX, codesite-noreply, 09:40
  • Issue 626 in lilypond: ottavation should accept markup, codesite-noreply, 09:12
• May 27, 2008
  • Re: Line breaks don't work when beams span barlines, Graham Percival, 23:50
  • Line breaks don't work when beams span barlines, Jesse Engle, 21:57
• May 26, 2008
  • Re: Ottava brackets formatting [was Re: Quoted text (was Re: When is "-" required in articulations?)], Neil Puttock, 10:42
  • Re: Crescendi overlapping bars, should be able to stop at first note after the bar, Erlend Aasland, 09:10
  • Re: Crescendi overlapping bars, should be able to stop at first note after the bar, Mats Bengtsson, 09:05
  • Crescendi overlapping bars, should be able to stop at first note after the bar, gringer, 08:30
  • Re: \acciaccatura produces extra double bar when using multiple staves, Mats Bengtsson, 03:34
  • Re: Ottava brackets formatting [was Re: Quoted text (was Re: When is "-" required in articulations?)], John Mandereau, 03:03
• May 25, 2008
  • Re: Ottava brackets formatting [was Re: Quoted text (was Re: When is "-" required in articulations?)], Neil Puttock, 11:43
  • Ottava brackets formatting [was Re: Quoted text (was Re: When is "-" required in articulations?)], John Mandereau, 08:46
  • \acciaccatura produces extra double bar when using multiple staves, Wim van Dommelen, 08:10
  • Re: Quoted text (was Re: When is "-" required in articulations?), Graham Percival, 05:00
  • Re: Quoted text (was Re: When is "-" required in articulations?), Neil Puttock, 04:52
  • Re: Quoted text (was Re: When is "-" required in articulations?), Graham Percival, 03:29
• May 24, 2008
  • arpeggio on chord notated with separate voices, Steven McDougall, 21:57
  • Re: Quoted text (was Re: When is "-" required in articulations?), Neil Puttock, 19:00
  • Re: Quoted text (was Re: When is "-" required in articulations?), Graham Percival, 18:04
  • post-score markup included with -dpreview, Arvid Grøtting, 17:03
  • Re: Quoted text (was Re: When is "-" required in articulations?), John Mandereau, 10:23
  • Issue 626 in lilypond: ottavation should accept markup, codesite-noreply, 10:22
• May 23, 2008
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 22:32
  • Re: Quoted text (was Re: When is "-" required in articulations?), Graham Percival, 21:18
  • Re: Issue 427 in lilypond: ugly collision slur and phrasing slur, Graham Percival, 18:42
  • Re: Issue 427 in lilypond: ugly collision slur and phrasing slur, Andrew Hawryluk, 17:46
• May 21, 2008
  • Re: Minor vim syntax improvements, Graham Percival, 06:45
  • Re: Minor vim syntax improvements, John Mandereau, 05:51
• May 20, 2008
  • Re: Minor vim syntax improvements, Joe Neeman, 23:11
  • yoyoyoyoy, Sally, 23:00
  • Re: Minor vim syntax improvements, Graham Percival, 22:58
  • Re: Minor vim syntax improvements, Jay Anderson, 21:44
  • Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby, codesite-noreply, 18:36
  • Re: musicxml2ly crash when reading breves, Neil Puttock, 16:58
  • Re: musicxml2ly crash when reading breves, Valentin Villenave, 12:20
  • Re: musicxml2ly crash when reading breves, David Fletcher, 12:04
  • Re: Minor vim syntax improvements, Graham Percival, 03:44
• May 19, 2008
  • Issue 268 in lilypond: lilypond -dpreview crops too much, codesite-noreply, 17:00
  • Re: pitchedtrill accidental problem, Valentin Villenave, 13:53
  • Re: pitchedtrill accidental problem, Han-Wen Nienhuys, 12:03
  • Re: Regression test different to normal compile., Han-Wen Nienhuys, 12:01
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 11:59
  • Re: pitchedtrill accidental problem, Risto Vääräniemi, 07:58
  • Re: Multiple copies of LilyPond in Windows, Trevor Daniels, 06:37
  • Re: Regression test different to normal compile., Matthew Rowles, 05:16
• May 18, 2008
  • Re: pitchedtrill accidental problem, Valentin Villenave, 17:57
  • Re: pitchedtrill accidental problem, Mats Bengtsson, 17:41
  • Issue 623 in lilypond: \addlyrics vertically misplaces Lyrics when instrumentName is set, codesite-noreply, 17:36
  • Re: Lyrics vertically misplaced using instrument name, Valentin Villenave, 17:36
  • Re: pitchedtrill accidental problem, Valentin Villenave, 17:31
  • Re: Lyrics vertically misplaced using instrument name, Mats Bengtsson, 16:27
  • Re: pitchedtrill accidental problem, Neil Puttock, 15:17
  • Re: Regression test different to normal compile., Neil Puttock, 14:59
  • Re: pitchedtrill accidental problem, Valentin Villenave, 12:24
  • Issue 524 in lilypond: pitched trill loses accidental, codesite-noreply, 12:19
  • Re: pitchedtrill accidental problem, Neil Puttock, 11:36
  • Re: Lyrics vertically misplaced using instrument name, Luc, 06:54
  • Re: Regression test different to normal compile., Graham Percival, 06:52
  • Re: Regression test different to normal compile., Matthew Rowles, 06:43
  • Re: pitchedtrill accidental problem, Valentin Villenave, 05:40
  • Issue 624 in lilypond: Regression: wrong trill script horizontal alignement when using pitchedTrill, codesite-noreply, 05:35
  • Re: slurs, key signatures, and bugs 379 & 427, Valentin Villenave, 05:20
  • Issue 379 in lilypond: ugly slur with key signature and linebreak, codesite-noreply, 05:11
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 05:07
  • Re: \once \override Beam, Valentin Villenave, 05:03
  • Re: Regression test different to normal compile., Valentin Villenave, 04:52
  • Issue 623 in lilypond: \addlyrics vertically misplaces Lyrics when instrumentName is set, codesite-noreply, 04:46
  • Re: Lyrics vertically misplaced using instrument name, Valentin Villenave, 04:46
  • Regression test different to normal compile., Matthew Rowles, 03:46
  • Lyrics vertically misplaced using instrument name, Robert Schröter, 03:30
  • Issue 585 in lilypond: Regression: Bass figures collapsing, codesite-noreply, 02:56
  • Issue 619 in lilypond: Regression: suggestAccidentals is broken, codesite-noreply, 02:52
• May 17, 2008
  • Issue 501 in lilypond: moving Bar_engraver into lyrics raises bar numbers, codesite-noreply, 21:18
  • Issue 488 in lilypond: flags take up space in other voice's tuplet, codesite-noreply, 21:14
  • Minor vim syntax improvements, Jay Anderson, 19:37
  • Issue 618 in lilypond: chords that include a 2nd can collide with other voices, codesite-noreply, 07:38
  • Issue 614 in lilypond: OttavaBracket left edge height not working, codesite-noreply, 07:34
  • Issue 622 in lilypond: Rests cause cross-staff havoc, codesite-noreply, 04:57
  • Issue 463 in lilypond: switching on and off followVoice, codesite-noreply, 04:53
  • Issue 622 in lilypond: Rests cause cross-staff havoc, codesite-noreply, 04:37
• May 16, 2008
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Joe Neeman, 18:50
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew Rowles, 18:44
• May 15, 2008
  • Re: pitchedtrill accidental problem, karim haddad, 12:31
  • slurs, key signatures, and bugs 379 & 427, Andrew Hawryluk, 01:27
• May 14, 2008
  • Re: pitchedtrill accidental problem, Neil Puttock, 16:51
  • pitchedtrill accidental problem, karim haddad, 12:21
  • Re: \once \override Beam, karim haddad, 12:08
  • Re: \once \override Beam, Mats Bengtsson, 04:10
  • Re: Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, Mats Bengtsson, 04:04
  • Re: \once \override Beam, Valentin Villenave, 02:47
• May 13, 2008
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew Rowles, 22:21
  • Issue 461 in lilypond: enharmonic ties, codesite-noreply, 15:07
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 15:02
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Neil Puttock, 14:51
  • re: \once \override Beam, karim haddad, 12:37
  • \once \override Beam doesn't work anymore?, karim haddad, 12:28
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew Rowles, 08:38
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew Rowles, 05:38
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Graham Percival, 03:37
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Francisco Vila, 03:33
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 03:22
  • Re: Collision between dynamics and bar line in GrandStaff, Valentin Villenave, 03:18
  • Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), codesite-noreply, 03:18
  • Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., codesite-noreply, 01:43
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 01:37
• May 12, 2008
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew Rowles, 21:57
  • Collision between dynamics and bar line in GrandStaff, George Macon, 21:55
  • Issue 461 in lilypond: enharmonic ties, codesite-noreply, 19:08
  • Issue 461 in lilypond: enharmonic ties, codesite-noreply, 17:15
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 16:39
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Neil Puttock, 15:42
  • Re: Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, Mats Bengtsson, 08:59
• May 11, 2008
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew, 21:52
  • Re: Issue 614 in lilypond: OttavaBracket left edge height not working, Matthew, 21:38
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 19:56
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 18:04
• May 09, 2008
  • Issue 619 in lilypond: Regression: suggestAccidentals is broken, codesite-noreply, 13:54
  • Issue 619 in lilypond: Regression: suggestAccidentals is broken, codesite-noreply, 12:48
  • Issue 619 in lilypond: Regression: suggestAccidentals is broken, codesite-noreply, 08:16
• May 08, 2008
  • Issue 618 in lilypond: chords that include a 2nd can collide with other voices, codesite-noreply, 13:43
• May 06, 2008
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, Mats Bengtsson, 03:47
• May 05, 2008
  • Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, codesite-noreply, 17:48
  • Issue 617 in lilypond: X-offset should take the specified alignment method into account, codesite-noreply, 17:25
  • Re: feedback to the latex-program option of lilypond-book, Till Rettig, 13:58
  • Re: Issue 617 in lilypond: X-offset should take the specified alignment method into account, Mats Bengtsson, 07:39
  • Issue 617 in lilypond: X-offset should take the specified alignment method into account, codesite-noreply, 06:53
  • Re: Issue 617 in lilypond: self-alignment-X doesn't work when X-offset is overridden, Mats Bengtsson, 06:36
• May 04, 2008
  • Issue 617 in lilypond: self-alignment-X doesn't work when X-offset is overridden, codesite-noreply, 16:15
  • Issue 617 in lilypond: self-alignment-X doesn't work when X-offset is overridden, codesite-noreply, 14:21
• May 03, 2008
  • Re: IR: errors in Backend docs for Grobs, Graham Percival, 18:29
  • Re: regressions- tablature: stems missing, Graham Percival, 18:25
  • Issue 616 in lilypond: tablature-banjo.ly fails in 2.11.45, codesite-noreply, 18:25
  • regressions- tablature: stems missing, Stan Sanderson, 15:14
  • Issue 461 in lilypond: enharmonic ties, codesite-noreply, 03:46
  • Issue 458 in lilypond: handling ties from different voices, codesite-noreply, 03:20
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 03:12
  • Issue 461 in lilypond: enharmonic ties, codesite-noreply, 03:08
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 03:04
  • Issue 458 in lilypond: handling ties from different voices, codesite-noreply, 00:48
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 00:44
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 00:40
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 00:36
• May 02, 2008
  • Re: Bad encoding of certain characters in vocal.itely, Graham Percival, 19:52
  • Bad encoding of certain characters in vocal.itely, Francisco Vila, 19:43
  • I think I found a bug in version 45 of lilypond and tablature, Daniel Tonda, 17:20
  • Issue 558 in lilypond: Spanner 'Hairpin' error when a MultiMeasureRest occurs after a line break, codesite-noreply, 07:43
  • Issue 378 in lilypond: lyrics misplaced with Completion_heads_engraver, codesite-noreply, 07:38
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 02:26
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 02:11
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 02:00
  • Issue 458 in lilypond: handling ties from different voices, codesite-noreply, 01:52
• May 01, 2008
  • Re: IR: errors in Backend docs for Grobs, Han-Wen Nienhuys, 23:06
  • Issue 591 in lilypond: Left edge of hairpin aligns with arpeggio, codesite-noreply, 23:05
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 22:29
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 22:25
  • Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, codesite-noreply, 18:46
  • Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, codesite-noreply, 18:25
  • Issue 397 in lilypond: collision pitchedTrill and tie, codesite-noreply, 18:16
  • Issue 302 in lilypond: bad shape for tied notes in different clefs, codesite-noreply, 18:12
  • Issue 458 in lilypond: handling ties from different voices, codesite-noreply, 18:08
  • Issue 298 in lilypond: ties, polyphonic, articulation collision, codesite-noreply, 17:58
  • Issue 455 in lilypond: wanted: vertical slur instead of arpeggio, codesite-noreply, 17:54
  • Issue 521 in lilypond: \repeatTie direction depends on next note (?), codesite-noreply, 17:33
  • Issue 143 in lilypond: \setTextCresc incorrectly applied only once, codesite-noreply, 17:27
  • Issue 434 in lilypond: unwanted direction change of broken tie, codesite-noreply, 17:23
  • Issue 592 in lilypond: Regression: Tie direction reverse incorrectly on a middle-staff note, codesite-noreply, 17:19
  • Issue 141 in lilypond: harmonizing vertical tie positions, codesite-noreply, 17:15
  • Issue 440 in lilypond: Tie direction reverse incorrectly between whole notes tied across line breaks, codesite-noreply, 17:11
  • Re: IR: errors in Backend docs for Grobs, Neil Puttock, 16:56
  • Issue 585 in lilypond: Regression: Bass figures collapsing, codesite-noreply, 16:25
  • Issue 585 in lilypond: Regression: Bass figures collapsing, codesite-noreply, 16:11
  • Re: feedback to the latex-program option of lilypond-book, John Mandereau, 15:26
  • Issue 578 in lilypond: Regression: Completion heads mess up lyrics, codesite-noreply, 15:24
  • Issue 615 in lilypond: lilypond-book 'relative' fragment option should imply 'fragment', codesite-noreply, 14:56
  • Re: IR: errors in Backend docs for Grobs, Han-Wen Nienhuys, 14:34
  • Re: IR: errors in Backend docs for Grobs, Neil Puttock, 12:27
  • Re: IR: errors in Backend docs for Grobs, Han-Wen Nienhuys, 12:11
  • Re: Typo in documentation, Graham Percival, 04:01
  • Re: Typo in documentation, Graham Percival, 03:50
  • Re: Typo in documentation, Valentin Villenave, 03:46
  • Typo in documentation, Mike Morrison, 01:30

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc