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: Fri Oct 31 2008 19:19:33 -0400 Messages in reverse chronological order

[Next Period]

---

• October 31, 2008
  • Re: Windows V2.11.62 and V2.11.63 report version number as V2.11.61, Eluze, 19:19
  • Windows V2.11.62 and V2.11.63 report version number as V2.11.61, Ian Hulin, 19:00
  • Re: Music repeat type: "fold", Werner LEMBERG, 04:53
• October 30, 2008
  • Re: Music repeat type: "fold", Valentin Villenave, 20:40
  • Music repeat type: "fold", Peter Riegel, 19:40
• October 29, 2008
  • Issue 703 in lilypond: Enhancement: TabStaff should handle non-monotonic stringTunings, codesite-noreply, 12:45
  • Re: Enhancement request -- make TabStaff work properly with non-monotonic stringTunings, Valentin Villenave, 12:36
  • Enhancement request -- make TabStaff work properly with non-monotonic stringTunings, Carl D. Sorensen, 12:17
  • Issue 702 in lilypond: "Moment is not increasing" error when combining Lyrics in a sequential way, codesite-noreply, 06:03
  • Re: Lyrics provoke "Moment is not increasing" complaint, Valentin Villenave, 06:03
  • Re: Lyrics provoke "Moment is not increasing" complaint, Mats Bengtsson, 05:57
  • Issue 76 in lilypond: beams should not collide with accidentals, codesite-noreply, 05:17
  • Issue 701 in lilypond: Collision accidental / beam, codesite-noreply, 05:14
  • Re: Lyrics provoke "Moment is not increasing" complaint, Valentin Villenave, 05:11
  • Issue 702 in lilypond: "Moment is not increasing" error when two Lyrics do not start at the same time, codesite-noreply, 05:06
• October 28, 2008
  • Re: Accidentals colliding with beams, Patrick McCarty, 19:33
  • Re: Accidentals colliding with beams, Eluze, 09:00
  • Issue 654 in lilypond: Text spanner collides with system bracket after line break, codesite-noreply, 05:48
  • Issue 678 in lilypond: Enhancement: Add option to make moll chords small, codesite-noreply, 05:44
  • Re: Accidentals colliding with beams, Valentin Villenave, 05:41
  • Issue 700 in lilypond: \tempo alignment, codesite-noreply, 05:40
  • Issue 701 in lilypond: Collision accidental / beam, codesite-noreply, 05:36
  • Accidentals colliding with beams, Patrick McCarty, 05:10
• October 27, 2008
  • Re: Lyrics provoke "Moment is not increasing" complaint, Mats Bengtsson, 19:59
  • Re: Error in time signature change with grace note, Mats Bengtsson, 16:13
  • Re: Error in time signature change with grace note, Eluze, 11:38
  • Error in time signature change with grace note, Jim Sansing, 11:10
  • Re: Trojan Dropper TR/Dropper.Gen reported in guile.exe when installing on Windows, Han-Wen Nienhuys, 09:00
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 05:02
  • Re: can I put a bounty on a bug?, Valentin Villenave, 04:59
  • Issue 379 in lilypond: ugly slur with key signature and linebreak, codesite-noreply, 04:58
  • Re: can I put a bounty on a bug?, Mark Polesky, 04:23
• October 26, 2008
  • Re: Issue 400 in lilypond: collision clef and beam, Valentin Villenave, 07:54
  • Re: Issue 400 in lilypond: collision clef and beam, Graham Percival, 07:33
  • Issue 400 in lilypond: collision clef and beam, codesite-noreply, 05:56
  • Re: Trojan Dropper TR/Dropper.Gen reported in guile.exe when installing on Windows, Thomas Scharkowski, 04:19
• October 25, 2008
  • Re: Trojan Dropper TR/Dropper.Gen reported in guile.exe when installing on Windows, Francisco Vila, 19:39
  • Trojan Dropper TR/Dropper.Gen reported in guile.exe when installing on Windows, Roberto Ordóñez, 19:15
  • Re: Issue 699 in lilypond: unwanted character changes on Windows Vista, sdfgsdhdshd, 13:13
  • Issue 699 in lilypond: unwanted character changes on Windows Vista, codesite-noreply, 13:09
  • Issue 699 in lilypond: unwanted character changes on Windows Vista, codesite-noreply, 13:04
  • Issue 700 in lilypond: \tempo alignment, codesite-noreply, 04:05
• October 24, 2008
  • Re: Character change on Vista, Jonathan Kulp, 08:36
  • Issue 699 in lilypond: unwanted character changes on Windows Vista, codesite-noreply, 07:46
  • Re: Character change on Vista, Valentin Villenave, 07:46
  • Re: Character change on Vista, Trevor Daniels, 07:35
  • Re: Character change on Vista, Valentin Villenave, 07:02
  • Re: Confusing start for newcomers on Windows, Valentin Villenave, 06:59
  • Issue 698 in lilypond: Windows users should be offered a better first impression, codesite-noreply, 06:54
  • Issue 697 in lilypond: Path problem on Windows, codesite-noreply, 06:50
  • Issue 697 in lilypond: Path problem on Windows, codesite-noreply, 06:29
  • Re: Problem running LP on win32., Valentin Villenave, 06:28
  • Issue 697 in lilypond: Path problem on Windows, codesite-noreply, 06:25
  • Confusing start for newcomers on Windows, Francisco Vila, 06:20
  • Re: Character change on Vista, Trevor Daniels, 06:00
  • Re: Problem running LP on win32., Francisco Vila, 05:47
  • Re: Problem running LP on win32., Mats Bengtsson, 05:16
• October 23, 2008
  • Re: lilypond, Andrew Hawryluk, 20:19
  • lilypond, Gracia, 15:30
  • Re. OOoLilyPond, \include "language" does not work., Music Site of Larry Jackson, 08:30
  • Re: can I put a bounty on a bug?, Andrew Hawryluk, 00:52
• October 22, 2008
  • Re: Issue 696 in lilypond: Misplaced tuplet number collides with accidental when a kneed beam occurs, Eluze, 18:41
  • Issue 696 in lilypond: Misplaced tuplet number collides with accidental when a kneed beam occurs, codesite-noreply, 16:27
  • Issue 696 in lilypond: Misplaced tuplet number collides with accidental when a kneed beam occurs, codesite-noreply, 09:47
  • Re: Tuplet number placement (and collision), Eluze, 05:39
  • Issue 279 in lilypond: x-staff tuplets cause havoc, codesite-noreply, 04:56
  • Re: Tuplet number placement (and collision), Valentin Villenave, 04:52
  • Issue 696 in lilypond: Misplaced tuplet number when a cross-staff tuplet has a kneed beam, codesite-noreply, 04:51
  • Tuplet number placement (and collision), Patrick McCarty, 01:13
• October 21, 2008
  • Re: Index entries leading to @seealso, Patrick McCarty, 19:36
  • Index entries leading to @seealso, Trevor Daniels, 18:20
• October 20, 2008
  • Re: can I put a bounty on a bug?, Neil Puttock, 18:43
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 10:31
  • Issue 379 in lilypond: ugly slur with key signature and linebreak, codesite-noreply, 10:27
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 04:26
  • Re: can I put a bounty on a bug?, Valentin Villenave, 04:24
  • Issue 379 in lilypond: ugly slur with key signature and linebreak, codesite-noreply, 04:22
• October 19, 2008
  • can I put a bounty on a bug?, Andrew Hawryluk, 22:39
  • Re: 2.10.33 slur bug example, Valentin Villenave, 10:41
• October 18, 2008
  • Re: abc2ly crash, John Mandereau, 11:40
  • Re: 2.10.33 slur bug example, John Gilbert, 03:48
  • Re: 2.10.33 slur bug example, Graham Percival, 03:14
  • 2.10.33 slur bug example, John Gilbert, 03:10
• October 17, 2008
  • Problem with copying file, Ian Grainger, 16:40
  • abc2ly crash, Laura Conrad, 10:41
• October 16, 2008
  • Re: Issue 694 in lilypond: Enhancement: better support for microtone accidentals, Trevor Daniels, 07:10
  • Issue 556 in lilypond: fingeringOrientations affects cross-voices arpeggio, codesite-noreply, 07:03
  • Re: Spacing/Positioning of Arpeggios when fingerings are present, Valentin Villenave, 07:03
  • Re: Spacing/Positioning of Arpeggios when fingerings are present, Jonathan Kulp, 06:54
  • Re: vertical spacing issues v2.11.59, Valentin Villenave, 06:17
  • Re: vertical spacing issues v2.11.59, Valentin Villenave, 06:04
  • Re: Windows Vista, Mats Bengtsson, 05:05
  • Re: Spacing/Positioning of Arpeggios when fingerings are present, Mats Bengtsson, 04:57
• October 15, 2008
  • Spacing/Positioning of Arpeggios when fingerings are present, Jonathan Kulp, 19:56
  • Re: Windows Vista, Valentin Villenave, 12:59
  • Windows Vista, Deborah Luke, 12:15
  • Re: lilypond bug with tome changes ?, Valentin Villenave, 03:44
  • lilypond bug with tome changes ?, Jacques, 03:30
  • Re: erroneous error message, Valentin Villenave, 03:22
  • Re: vertical spacing issues v2.11.59, Valentin Villenave, 03:21
  • Issue 695 in lilypond: slurs may take too much vertical extent, codesite-noreply, 03:18
  • Re: ugly notation of text script + slur, Valentin Villenave, 03:18
  • Re: erroneous error message, Graham Percival, 01:28
  • erroneous error message, Didi Kanjahn, 01:15
  • vertical spacing issues v2.11.59, Didi Kanjahn, 01:10
• October 14, 2008
  • Re: ugly notation of text script + slur, Graham Percival, 21:15
  • Re: ugly notation of text script + slur, Patrick McCarty, 20:55
  • ugly notation of text script + slur, Graham Percival, 20:20
  • Re: Issue 694 in lilypond: Enhancement: better support for microtone accidentals, Graham Percival, 17:39
  • Re: Issue 694 in lilypond: Enhancement: better support for microtone accidentals, Trevor Daniels, 16:52
  • Issue 573 in lilypond: score-final mark mangles score-final tuplet bracket, codesite-noreply, 15:33
• October 13, 2008
  • Re: Documentation won't build, Patrick McCarty, 13:31
  • Re: Documentation won't build, Till Rettig, 12:48
  • Re: Issue 694 in lilypond: Enhancement: better support for microtone accidentals, Graham Percival, 12:24
  • Documentation won't build, Pietro Cerutti, 11:20
  • Issue 694 in lilypond: Enhancement: better support for microtone accidentals, codesite-noreply, 03:02
  • Issue 694 in lilypond: Enhancement: better support for microtone accidentals, codesite-noreply, 00:35
• October 12, 2008
  • Re: musicxml2ly bar-line support, Reinhold Kainhofer, 17:32
  • Issue 694 in lilypond: Enhancement: better support for microtone accidentals, codesite-noreply, 16:49
  • musicxml2ly bar-line support, Valentin Villenave, 08:30
• October 10, 2008
  • Re: Grace notes cause clef-change positioning problem, Jonathan Kulp, 16:42
  • Re: Grace notes cause clef-change positioning problem, Werner LEMBERG, 16:24
  • Re: Grace notes cause clef-change positioning problem, Jonathan Kulp, 15:16
  • Re: Grace notes cause clef-change positioning problem, Wilbert Berendsen, 15:04
  • Re: Grace notes cause clef-change positioning problem, Wilbert Berendsen, 14:58
  • Grace notes cause clef-change positioning problem, Jonathan Kulp, 14:51
  • Re: Lilypond documentation Custos, Trevor Daniels, 13:17
  • Add to wishlist: unusual Alto Clef, Jonathan Kulp, 10:06
  • Issue 155 in lilypond: \parenthesize should include accidentals as well as note heads, codesite-noreply, 09:47
• October 09, 2008
  • Issue 693 in lilypond: Request: alternate C clef glyph, codesite-noreply, 13:16
  • Lilypond documentation Custos, Martial, 12:51
  • Issue 693 in lilypond: Request: alternate C clef glyph, codesite-noreply, 11:53
  • Issue 453 in lilypond: \scaleDurations adds too many beams to tremolos, codesite-noreply, 06:52
  • Issue 693 in lilypond: Request: alternate C clef glyph, codesite-noreply, 04:30
• October 08, 2008
  • Issue 692 in lilypond: slurs look bad when forced on the same direction as the stems, codesite-noreply, 10:05
  • Issue 692 in lilypond: slurs look bad when forced on the same direction as the stems, codesite-noreply, 10:00
• October 06, 2008
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 18:43
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 17:40
  • Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, codesite-noreply, 17:25
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Valentin Villenave, 17:19
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 17:18
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 16:13
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Reinhold Kainhofer, 15:54
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Neil Puttock, 15:01
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Valentin Villenave, 13:00
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 12:58
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Reinhold Kainhofer, 11:50
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Valentin Villenave, 06:53
  • Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration, codesite-noreply, 06:52
• October 05, 2008
  • Issue 683 in lilypond: \paper variable syntax changes, codesite-noreply, 18:45
  • Issue 661 in lilypond: Unwanted TextScript offset when overriding TrillSpanner style, codesite-noreply, 18:41
  • Re: Lilypond documentation web site bug, Valentin Villenave, 18:39
  • typo in the Tips and Tricks document, Matej Kosik, 17:20
  • Issue 683 in lilypond: \paper variable syntax changes, codesite-noreply, 17:01
  • Issue 661 in lilypond: Unwanted TextScript offset when overriding TrillSpanner style, codesite-noreply, 16:57
  • Re: lilypond-book fails to unindent after instrument name, Neil Puttock, 16:33
  • Lilypond documentation web site bug, Dick Valentine, 16:15
  • Re: lilypond-book fails to unindent after instrument name, Patrick McCarty, 15:44
  • AW: AW: Error in Documentation "1.4 Music representation"?, Christian Keil, 06:38
  • AW: Error in Documentation "1.4 Music representation"?, Robin Bannister, 06:25
  • AW: AW: Error in Documentation "1.4 Music representation"?, Christian Keil, 06:03
  • Re: AW: Error in Documentation "1.4 Music representation"?, Graham Percival, 05:41
  • AW: Error in Documentation "1.4 Music representation"?, Christian Keil, 05:32
  • Re: Error in Documentation "1.4 Music representation"?, Graham Percival, 04:06
  • Error in Documentation "1.4 Music representation"?, Christian Keil, 01:25
• October 04, 2008
  • Re: menu bars missing 2.11.61, Patrick McCarty, 15:58
  • menu bars missing 2.11.61, Robin Bannister, 06:50
• October 01, 2008
  • Issue 429 in lilypond: new accidental style: teaching, codesite-noreply, 18:44
  • Issue 690 in lilypond: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff, codesite-noreply, 14:06
  • Issue 487 in lilypond: stems of beamed notes too long before staff change, codesite-noreply, 14:02
  • Re: problems with RemoveEmptyStaffContext in PianoStaff, Neil Puttock, 13:00
  • Re: problems with RemoveEmptyStaffContext in PianoStaff, Valentin Villenave, 08:44
  • Issue 690 in lilypond: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff, codesite-noreply, 08:42
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Alexander Kobel, 08:24
  • Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Valentin Villenave, 07:23
  • Tempo mark doesn't forget explicitly given bpm, v. 2.11.60, Thies Albrecht, 04:51

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc