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: Tue May 31 2011 18:17:05 -0400 Messages in reverse chronological order

[Next Period]

---

• May 31, 2011
  • Re: Issue 1667 in lilypond: silly bug about thinking cross-staff beams, lilypond, 18:17
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 18:13
  • Re: Issue 1674 in lilypond: String-match unbound function unavailable in lilypond, lilypond, 18:08
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 18:04
  • Re: Partcombine, Xavier Scheuer, 16:46
  • Partcombine, Nels Daily, 16:19
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, Colin Campbell, 09:17
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, Phil Holmes, 05:06
  • Re: Issue 1359 in lilypond: GUB always rebuilds everywhere, lilypond, 04:27
• May 30, 2011
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, Colin Campbell, 23:04
  • Re: Issue 1359 in lilypond: GUB always rebuilds everywhere, lilypond, 18:14
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 15:39
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 15:35
  • Re: Strange \repeat tremolo, Phil Holmes, 09:38
  • Issue 1676 in lilypond: Tremolo with change staff produces false dotted note, lilypond, 09:38
  • Re: Strange \repeat tremolo, Reinhold Kainhofer, 08:56
  • Re: Issue 1675 in lilypond: lilypond as an html5 app, lilypond, 07:33
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 07:06
  • Issue 1675 in lilypond: lilypond as an html5 app, lilypond, 06:53
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 06:48
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, David Kastrup, 02:53
  • Re: Issue 1671 in lilypond: Vertical spacing: undesired figured bass stretching, lilypond, 01:38
• May 29, 2011
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 21:50
  • Re: Issue 1671 in lilypond: Vertical spacing: undesired figured bass stretching, lilypond, 20:25
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 20:21
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 20:17
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 20:13
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 20:09
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 20:05
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 19:16
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 18:49
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', Keith OHara, 18:34
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 17:34
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 17:30
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', Werner LEMBERG, 16:58
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', Keith OHara, 16:53
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 16:21
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 16:17
  • Re: Cross-staff beaming, address@hidden, 16:12
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 14:05
  • Re: Attachments on the tracker, Phil Holmes, 12:22
  • Re: Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 12:12
  • Re: Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 12:07
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 12:04
  • Re: Attachments on the tracker, Phil Holmes, 10:38
  • Re: Cross-staff beaming, Carl Sorensen, 09:01
  • Re: Attachments on the tracker, Carl Sorensen, 08:36
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 08:29
  • Re: Attachments on the tracker, Graham Percival, 07:57
  • Re: Cross-staff beaming, Hilary Snaden, 07:43
  • Re: Attachments on the tracker, Phil Holmes, 06:29
  • Attachments on the tracker, Phil Holmes, 06:20
  • Re: Cross-staff beaming, Phil Holmes, 06:11
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 06:02
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 05:44
  • Cross-staff beaming, Hilary Snaden, 05:24
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 04:11
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', David Kastrup, 02:24
• May 28, 2011
  • Re: Issue 1646 in lilypond: MIDI output on incorrect channels (using GUB build), lilypond, 22:32
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 15:41
  • Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem, lilypond, 15:21
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 15:01
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 14:55
  • Re: string-match unbound, Colin Campbell, 11:34
  • Issue 1674 in lilypond: String-match unbound function unavailable in lilypond, lilypond, 11:33
  • Re: Balloon fails with cross-staff arpeggios, Phil Holmes, 10:32
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 09:11
  • Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 08:07
  • Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem, lilypond, 08:03
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 07:59
  • Re: Vertical spacing: undesired figured bass stretching, Nicolas Sceaux, 03:46
  • Re: Issue 1671 in lilypond: Vertical spacing: undesired figured bass stretching, lilypond, 01:57
  • Re: Issue 1667 in lilypond: silly bug about thinking cross-staff beams, lilypond, 00:12
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 00:05
• May 27, 2011
  • Re: Vertical spacing: undesired figured bass stretching, Colin Campbell, 23:49
  • Issue 1671 in lilypond: Vertical spacing: undesired figured bass stretching, lilypond, 23:48
  • Re: Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 22:54
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 18:40
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 15:15
  • Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 15:00
  • Re: Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 14:47
  • Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 14:43
  • Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 14:31
  • Issue 1667 in lilypond: silly bug about thinking cross-staff beams, lilypond, 13:49
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 13:29
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 13:25
  • Re: string-match unbound, Graham Percival, 13:15
  • Re: string-match unbound, Phil Holmes, 12:37
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 12:32
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 12:23
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 12:19
  • string-match unbound, Piers Titus, 12:15
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 12:14
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 12:10
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 12:06
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 12:02
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 11:22
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 11:10
  • Re: Further question about versions/verifying, Graham Percival, 11:08
  • Re: Page-label.ly, Phil Holmes, 10:55
  • Further question about versions/verifying, Phil Holmes, 10:52
  • Re: Issue 877 in lilypond: Ottava clefs may not look good, lilypond, 10:49
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 10:15
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 09:45
  • Re: Fingering positioning problem 2.13.61, Phil Holmes, 09:43
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 09:30
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 09:18
  • Re: Vertical spacing: undesired figured bass stretching, Joe Neeman, 09:15
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 09:08
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 09:00
  • Re: Fingering positioning problem 2.13.61, Nick Payne, 08:56
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 08:27
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 08:15
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 07:47
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 07:32
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 07:20
  • Re: Fingering positioning problem 2.13.61, Phil Holmes, 07:17
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 07:01
  • Fingering positioning problem 2.13.61, Nick Payne, 06:35
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 02:56
• May 26, 2011
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 15:17
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 15:13
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 11:34
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 11:30
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 11:26
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 10:56
  • Re: Issue 1659 in lilypond: convert-ly should check if it's in a comment or not, lilypond, 10:48
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 08:33
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 08:27
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 08:21
  • Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 08:17
  • Re: fretted-string-harmonics-in-tablature snippet, Phil Holmes, 08:17
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 08:13
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 06:27
  • Vertical spacing: undesired figured bass stretching, Nicolas Sceaux, 03:24
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 01:16
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 01:12
  • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 00:46
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 00:41
• May 25, 2011
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 16:26
  • Re: Issue 1646 in lilypond: MIDI output on incorrect channels (using GUB build), lilypond, 14:09
  • Re: Issue 877 in lilypond: Ottava clefs may not look good, lilypond, 14:05
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 14:01
  • Re: Issue 1659 in lilypond: convert-ly should check if it's in a comment or not, lilypond, 13:57
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 13:52
  • Re: Issue 1634 in lilypond: make find(1) work on BSDs, lilypond, 13:46
  • Re: fretted-string-harmonics-in-tablature snippet, Graham Percival, 13:42
  • Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 13:39
  • Re: Two predefined guitar fretboards typos genereate incorrect fret diagrams, Graham Percival, 13:39
  • Issue 1664 in lilypond: Add link to LSR on web site, lilypond, 11:50
  • Re: Issue 1412 in lilypond: programming error: Going back in MIDI time, David Kastrup, 11:36
  • RE: Incorrect placement of \grace with \repeat in combination with nested Staff, James Lowe, 11:24
  • Re: Issue 1412 in lilypond: programming error: Going back in MIDI time, lilypond, 11:15
  • Re: midiInstrument "choir aahs" changes to piano in 2.13.61, Tony Towers, 11:03
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 10:47
  • Incorrect placement of \grace with \repeat in combination with nested Staff, Ronald Pijnacker, 10:43
  • midiInstrument "choir aahs" changes to piano in 2.13.61, Tony Towers, 10:43
  • Issue 1663 in lilypond: Images missing on web site, lilypond, 10:21
• May 24, 2011
  • Re: midi & pdf disagree with conflicting tempo-changes, Colin Campbell, 23:32
  • Issue 1662 in lilypond: midi & pdf disagree with conflicting tempo-changes, lilypond, 23:31
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 18:15
  • Re: fretted-string-harmonics-in-tablature snippet, Federico Bruni, 17:22
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 12:44
  • midi & pdf disagree with conflicting tempo-changes, Mark Polesky, 12:26
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 12:19
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 12:06
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 09:14
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 09:10
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 08:58
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 08:50
  • Re: fretted-string-harmonics-in-tablature snippet, Dmytro O. Redchuk, 04:33
  • Re: Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 04:21
  • Re: MIDI ignores dynamics parallel to notes, Keith OHara, 00:32
  • Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 00:31
• May 23, 2011
  • Re: Issue 1654 in lilypond: Collision between lyrics and items on the next system, lilypond, 23:56
  • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 17:17
  • Re: MIDI ignores dynamics parallel to notes, Keith OHara, 16:43
  • Re: erroneous output of treble clef using staff size 18, Henning Plumeyer, 16:13
  • Re: fretted-string-harmonics-in-tablature snippet, Federico Bruni, 14:16
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 11:17
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, address@hidden, 11:02
  • Re: MIDI ignores dynamics parallel to notes, Dmytro O. Redchuk, 10:34
  • Re: Two predefined guitar fretboards typos genereate incorrect fret diagrams, Dmytro O. Redchuk, 10:23
  • Two predefined guitar fretboards typos genereate incorrect fret diagrams, K . Kellogg-Smith, 10:20
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 10:18
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 10:14
  • Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 09:39
  • Re: harmonicOn doesn't work in TabStaff, Dmytro O. Redchuk, 09:38
  • Re: fretted-string-harmonics-in-tablature snippet, Dmytro O. Redchuk, 09:34
  • Issue 1659 in lilypond: convert-ly should check if it's in a comment or not, lilypond, 09:22
  • Re: test of convert-ly, Dmytro O. Redchuk, 09:22
  • Re: Issue 1634 in lilypond: make find(1) work on BSDs, lilypond, 09:03
  • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 08:59
  • MIDI ignores dynamics parallel to notes, Richard Sabey, 06:06
• May 22, 2011
  • Re: erroneous output of treble clef using staff size 18, Francisco Vila, 19:09
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 17:33
  • Re: erroneous output of treble clef using staff size 18, Simon, 16:01
  • harmonicOn doesn't work in TabStaff, Federico Bruni, 15:52
  • fretted-string-harmonics-in-tablature snippet, Federico Bruni, 15:45
• May 21, 2011
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 17:45
  • Re: 2nd-voice \stemDown ignored with cross-staff stems, -Eluze, 16:45
  • 2nd-voice \stemDown ignored with cross-staff stems, Javier Ruiz-Alma, 15:22
  • Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 00:36
• May 19, 2011
  • Descargar, Santiago Medina, 20:30
  • Re: test of convert-ly, Carl Sorensen, 20:03
  • Re: Issue 1656 in lilypond: Broken link on German manuals page, lilypond, 08:05
  • Re: Bug with acciaccatura on beginning of staff, Phil Holmes, 04:37
• May 18, 2011
  • Re: Issue 1656 in lilypond: Broken link on German manuals page, lilypond, 14:41
  • Re: Balloon fails with cross staff arpeggio, Ralph Palmer, 14:30
  • Issue 1657 in lilypond: Balloon fails with cross-staff arpeggios, lilypond, 14:27
  • Re: Broken link on German manuals page, Ralph Palmer, 14:20
  • Issue 1656 in lilypond: Broken link on German manuals page, lilypond, 14:19
  • Bug with acciaccatura on beginning of staff, Michail M . Iglizky, 14:05
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 13:40
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 12:40
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 09:10
• May 17, 2011
  • Re: ppp on harmonics is too close to the bar line than normal notes, Marc Mouries, 22:02
  • Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 17:48
  • Re: LilyPond 2.13.61: MIDI names broken, Hans Aberg, 03:44
  • Re: midi.c: always false check, Keith OHara, 00:51
  • Re: LilyPond 2.13.61: MIDI names broken, Keith OHara, 00:38
• May 16, 2011
  • LilyPond 2.13.61: MIDI names broken, Hans Aberg, 18:00
  • Balloon fails with cross staff arpeggio, Colin Campbell, 15:20
  • midi.c: always false check, Nicolas Kaiser, 09:35
  • Re: Issue 1654 in lilypond: Collision between lyrics and raised rehearsal mark, lilypond, 09:33
  • Balloon fails with cross-staff arpeggios, Bertrand Bordage, 06:53
  • Re: Issue 877 in lilypond: Ottava clefs may not look good, lilypond, 05:26
• May 15, 2011
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 19:37
  • Re: Issue 1654 in lilypond: Collision between lyrics and raised rehearsal mark, lilypond, 18:30
  • Re: Issue 1653 in lilypond: Harmonic noteheads are not center-aligned on note column, lilypond, 18:16
  • Re: Issue 1654 in lilypond: Collision between lyrics and raised rehearsal mark, lilypond, 18:11
  • Re: Issue 1653 in lilypond: Dynamics markings shifted by \harmonic, lilypond, 16:20
  • Issue 1654 in lilypond: Collision between lyrics and raised rehearsal mark, lilypond, 11:31
• May 14, 2011
  • Re: ppp on harmonics is too close to the bar line than normal notes, Colin Campbell, 22:43
  • Issue 1653 in lilypond: Dynamics markings shifted by \harmonic, lilypond, 22:43
  • ppp on harmonics is too close to the bar line than normal notes, Marc Mouries, 19:49
  • Broken link on German manuals page, Martin von Gagern, 16:20
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 15:24
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 05:15
• May 13, 2011
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 22:11
  • Re: Issue 1651 in lilypond: Triplet direction depends on rest length, lilypond, 02:33
  • Re: Issue 1646 in lilypond: MIDI output on incorrect channels (using GUB build), lilypond, 02:23
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 00:52
• May 12, 2011
  • Re: Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 19:32
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 16:45
  • Re: erroneous output of treble clef using staff size 18, -Eluze, 12:50
  • Re: erroneous output of treble clef using staff size 18, Phil Holmes, 12:02
  • Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 10:21
  • erroneous output of treble clef using staff size 18, Simon, 10:15
  • Re: Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 04:57
  • Re: Direction of tuplet bracket and number depends on length of rest, Phil Holmes, 04:53
  • Issue 1651 in lilypond: Triplet direction depends on rest length, lilypond, 04:53
  • Re: Direction of tuplet bracket and number depends on length of rest, Henning Plumeyer, 03:02
• May 11, 2011
  • Re: Issue 1647 in lilypond:, lilypond, 20:25
  • Re: Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 18:09
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 18:05
  • Direction of tuplet bracket and number depends on length of rest, Henning, 17:29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 09:34
  • Re: using multiple \header in a block prints only the latest items, Ralph Palmer, 07:24
  • Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 07:22
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 00:00
• May 10, 2011
  • Re: Issue 1649 in lilypond: ly:arpeggio::brew-chord-bracket can lead to tight horizontal spacing, lilypond, 22:05
  • Issue 1649 in lilypond: ly:arpeggio::brew-chord-bracket can lead to tight horizontal spacing, lilypond, 21:23
  • Re: page break after book header block/before bookpart, -Eluze, 18:20
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 15:46
  • Re: page break after book header block/before bookpart, Graham Percival, 15:22
  • RE: page break after book header block/before bookpart, James Lowe, 13:21
  • Re: page break after book header block/before bookpart, Graham Percival, 13:16
  • page break after book header block/before bookpart, -Eluze, 03:23
• May 09, 2011
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 23:43
  • using multiple \header in a block prints only the latest items, -Eluze, 19:02
  • Fwd: LilyPond Windows installer entirely erases the PATH environmentvariable, James Lowe, 18:42
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 18:25
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 17:51
  • Re: Ossia staff verse order, Phil Holmes, 12:24
  • Re: Ossia staff verse order, Trevor Daniels, 12:19
  • Ossia staff verse order, Phil Holmes, 11:49
  • Re: Issue 1560 in lilypond: Lyrics can not be aligned below ossia staff, lilypond, 11:44
• May 08, 2011
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 07:07
  • Re: LilyPond Windows installer entirely erases the PATH environmentvariable, Phil Holmes, 06:40
  • RE: LilyPond Windows installer entirely erases the PATH environment variable, James Lowe, 06:38
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 02:30
• May 07, 2011
  • Re: LilyPond Windows installer entirely erases the PATH environment variable, Colin Campbell, 23:56
  • LilyPond Windows installer entirely erases the PATH environment variable, Zachary Northrup, 23:05
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 20:10
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 13:26
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 13:22
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 13:16
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 13:12
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 10:59
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 10:55
  • Re: Stem length on beamed notes incorrect in 2.13.61, address@hidden, 10:14
  • Stem length on beamed notes incorrect in 2.13.61, Nick Payne, 04:49
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 03:59
  • Re: MIDI skips note if another voice struck it previously, Keith OHara, 03:42
  • Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 03:39
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 01:31
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 00:55
  • Re: MIDI skips note if another voice struck it previously, Keith OHara, 00:29
  • Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 00:23
• May 06, 2011
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 21:20
  • Re: Issue 877 in lilypond: Ottava clefs may not look good, lilypond, 18:39
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 07:02
  • Re: MIDI skips note if another voice struck it previously, Phil Holmes, 06:03
  • Re: MIDI skips note if another voice struck it previously, Janek Warchoł, 05:39
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 03:49
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 03:38
• May 05, 2011
  • Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 23:45
  • Re: Issue 1318 in lilypond: midi2ly broken on Mac OS X, lilypond, 23:39
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 23:34
  • Re: Issue 1318 in lilypond: midi2ly broken on Mac OS X, lilypond, 23:10
  • Re: Issue 1646 in lilypond: MIDI output on incorrect channels (using GUB build), lilypond, 12:11
  • Re: Beam avoidance of other voices and stem length for beamed notes, address@hidden, 11:32
  • Re: Issue 1318 in lilypond: midi2ly broken on Mac OS X, lilypond, 11:12
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 08:20
  • Re: Beam avoidance of other voices and stem length for beamed notes, Nick Payne, 05:13
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within gracenotes, Trevor Daniels, 04:54
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 04:45
  • Issue 1646 in lilypond: MIDI output on incorrect channels (using GUB build), lilypond, 04:04
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 03:08
  • Re: Issue 1644 in lilypond: get_working_directory () issue?, lilypond, 03:04
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 03:00
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 02:56
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 02:51
  • Re: Issue 1640 in lilypond: Consecutive glissandos not typeset, lilypond, 02:47
  • Re: Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all, lilypond, 02:41
  • Re: Issue 1644 in lilypond: get_working_directory () issue?, lilypond, 01:37
  • Re: Issue 1644 in lilypond: get_working_directory () issue?, lilypond, 01:33
• May 04, 2011
  • Re: Beam avoidance of other voices and stem length for beamed notes, address@hidden, 23:21
  • Re: Cyclical/mutual includes not detected, Colin Campbell, 21:14
  • Re: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, Colin Campbell, 21:03
  • Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 21:02
  • Re: Wrong version of midi.so in LilyPond 2.13.60, Colin Campbell, 20:58
  • Re: One warning in flower, Graham Percival, 18:20
  • Beam avoidance of other voices and stem length for beamed notes, Nick Payne, 18:17
  • Re: Wrong version of midi.so in LilyPond 2.13.60, Graham Percival, 18:14
  • Re: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, Mike Solomon, 13:07
  • Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, Bertrand Bordage, 12:58
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 12:49
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 12:44
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 12:40
  • Re: Another cross-staff beaming problem?, Phil Holmes, 12:15
  • LilyPond Versions (was Re: Issue 1622 in lilypond: Dynamic spanner not printed within gracenotes), Carl Sorensen, 11:25
  • Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 09:20
  • Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 09:16
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 09:12
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 09:08
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within gracenotes, Colin Campbell, 09:06
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 09:04
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 09:00
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 08:56
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 08:52
  • Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 08:48
  • Re: Part Combiner problems, Reinhold Kainhofer, 08:07
  • Re: tags in parallel music gives "Bars in parallel music don't have the same length", Ralph Palmer, 07:57
  • Re: Doc: LSR: midi, Ralph Palmer, 07:44
  • Re: One warning in flower, Ralph Palmer, 07:42
  • Issue 1644 in lilypond: get_working_directory () issue?, lilypond, 07:41
  • Re: Doc: LSR: midi, Ralph Palmer, 07:35
  • Re: Wrong version of midi.so in LilyPond 2.13.60, Ralph Palmer, 07:32
  • Re: Part Combiner problems, Ralph Palmer, 07:29
  • Issue 1643 in lilypond: Part Combine problems, lilypond, 07:28
  • Re: Tuplet line collides with fingering, Ralph Palmer, 07:21
  • Issue 1642 in lilypond: Tuplet bracket collides with slur, lilypond, 07:20
  • Re: Steams in second voice with auto beaming are broken, Francisco Vila, 07:08
  • Steams in second voice with auto beaming are broken, Roman V . Kiseliov, 06:55
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, Keith OHara, 04:41
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within gracenotes, Trevor Daniels, 04:29
• May 03, 2011
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, Colin Campbell, 21:08
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 16:49
  • Re: Issue 1616 in lilypond: old website link gives false doc suggestion info, lilypond, 15:35
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 15:31
  • Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash, lilypond, 15:14
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 15:10
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 15:06
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, Keith OHara, 15:01
  • Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 14:57
  • Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 14:53
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 14:49
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 14:38
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 14:34
  • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 14:30
  • Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 14:26
  • Re: Another cross-staff beaming problem?, Keith OHara, 13:40
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 11:45
  • Re: Another cross-staff beaming problem?, Phil Holmes, 09:59
  • Re: Another cross-staff beaming problem?, Colin Campbell, 09:07
  • Another cross-staff beaming problem?, Phil Holmes, 04:15
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 00:48
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 00:24
• May 02, 2011
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 22:26
  • Re: TabStaff and glissando from note to chord (or the other way around), Federico Bruni, 16:25
  • Re: Issue 1612 in lilypond: Change staff produces long stems, Carl Sorensen, 09:53
  • Re: Issue 1612 in lilypond: Change staff produces long stems, address@hidden, 09:49
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 09:46
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 09:38
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 09:34
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah no longer likes git fetch --depth, lilypond, 09:27
  • Re: Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 09:23
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 09:19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 09:15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 09:10
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 09:06
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 09:02
  • Re: Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 08:58
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 08:54
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 08:25
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 08:21
  • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 08:16
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 08:12
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 08:08
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, Helge Hafting, 05:28
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 01:56
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 01:48
  • Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 01:44
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 01:32
• May 01, 2011
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 21:09
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 19:43
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah no longer likes git fetch --depth, lilypond, 18:41
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 16:19
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 14:55
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheckwarnings, Phil Holmes, 13:32
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 13:24
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah no longer likes git fetch --depth, lilypond, 13:02
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 12:37
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 11:55
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 10:06
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 09:59
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 09:55
  • RE: Wrong ties when moving Tie_engraver from Voice to Staff, Helge Hafting, 07:37
  • Re: TabStaff and glissando from note to chord (or the other way around), Phil Holmes, 06:23
  • TabStaff and glissando from note to chord (or the other way around), Federico Bruni, 05:52

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc