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 Aug 31 2007 19:00:46 -0400 Messages in reverse chronological order

[Next Period]

---

• August 31, 2007
  • Re: 2.11.30 segmentation fault, Trevor Bača, 19:00
  • Re: 2.11.30 segmentation fault, Joe Neeman, 18:31
  • Re: Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), Joe Neeman, 18:29
  • music writing for choir, Mike Ware, 15:20
  • Issue 432 in lilypond: odd layout when Mar_engraver is moved into Staff, codesite-noreply, 14:10
  • Re: 2.11.30 segmentation fault, Han-Wen Nienhuys, 12:34
  • Re: Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), Han-Wen Nienhuys, 10:35
  • Re: 2.11.30 segmentation fault, Trevor Bača, 10:10
  • Re: 2.11.30 segmentation fault, Valentin Villenave, 09:56
  • Re: Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), Joe Neeman, 09:47
  • 2.11.30 segmentation fault, Trevor Bača, 09:17
  • Issue 433 in lilypond: 2.11.30 segmentation fault, codesite-noreply, 09:16
  • Issue 63 in lilypond: volta brackets not vertically aligned, codesite-noreply, 04:59
  • Unbeamed notes after a cadenza and an appogiatura, Nicolas Klutchnikoff, 02:35
• August 30, 2007
  • Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), codesite-noreply, 23:31
  • Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), codesite-noreply, 23:23
  • Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), codesite-noreply, 23:16
  • Issue 432 in lilypond: odd layout when Mar_engraver is moved into Staff, codesite-noreply, 22:26
  • Re: Alignment problem with RehearsalMark, Graham Percival, 22:25
  • Issue 431 in lilypond: menus in windows should be unicode, codesite-noreply, 22:22
  • Re: font is broken on WinXP Japanese, Graham Percival, 22:21
  • Issue 406 in lilypond: Feathered beams do not work with knees, codesite-noreply, 22:18
  • programming error: minimise_least_squares (): Nothing to minimise, Neil Puttock, 21:51
  • Cross-staff beam craziness (when down-markup combines with down-articulation), Trevor Bača, 20:55
  • Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation), codesite-noreply, 20:54
  • Re: No graphics in several pages, Gait Boxman, 09:36
  • Re: No graphics in several pages, Mats Bengtsson, 08:29
  • No graphics in several pages, Henning Plumeyer, 05:15
• August 29, 2007
  • Hara_kiri_engraver shouldn't handle both staves of a PianoStaff as separate single staves, Valentin Villenave, 12:47
• August 28, 2007
  • Issue 153 in lilypond: \once \set fails with MIDI instruments, codesite-noreply, 23:54
  • Issue 153 in lilypond: \once \set fails with MIDI instruments, codesite-noreply, 22:40
  • Issue 367 in lilypond: layout-set-staff-size doesn't change the distance between the staff lines, codesite-noreply, 22:22
  • Issue 410 in lilypond: tie too short when clef change at end of system, codesite-noreply, 18:11
  • Issue 426 in lilypond: very short tie due to key signature, codesite-noreply, 18:07
  • Issue 426 in lilypond: very short tie due to key signature, codesite-noreply, 18:03
  • Issue 425 in lilypond: input/regression/spacing-non-adjacent-column2.ly, codesite-noreply, 08:48
  • Issue 424 in lilypond: input/regression/accidental-forced-tie.ly, codesite-noreply, 08:44
  • Re: Ties are missing in pdf / ps file, Mats Bengtsson, 08:18
  • Ties are missing in pdf / ps file, Edgar Riegger, 08:06
  • Re: Alignment problem with RehearsalMark, Mats Bengtsson, 02:05
• August 27, 2007
  • problem with lilypond from the command line, Jake Rundall, 15:05
  • Issue 429 in lilypond: new accidental style: teaching, codesite-noreply, 10:59
  • font is broken on WinXP Japanese, YAMASHINA Hio, 10:55
  • Re: Issue 427 in lilypond: ugly collision slur and phrasing slur, Arvid Grøtting, 06:36
  • Issue 64 in lilypond: volta brackets below chords instead of above them, codesite-noreply, 05:49
  • Issue 64 in lilypond: volta brackets below chords instead of above them, codesite-noreply, 05:45
  • Issue 64 in lilypond: volta brackets below chords instead of above them, codesite-noreply, 05:27
  • Issue 429 in lilypond: new accidental style: teaching, codesite-noreply, 05:23
  • Issue 424 in lilypond: input/regression/accidental-forced-tie.ly, codesite-noreply, 05:19
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 05:18
  • Issue 428 in lilypond: collision avoidance fails sometimes with simultaneous voices, codesite-noreply, 05:15
  • Issue 427 in lilypond: ugly collision slur and phrasing slur, codesite-noreply, 05:11
  • Re: corrupt collision avoiding when using simultaneous voices, Graham Percival, 05:11
  • Re: Should slurs really start before the key signature?, Graham Percival, 05:05
  • Issue 426 in lilypond: very short tie due to key signature, codesite-noreply, 05:03
  • Re: Tie too short after break when staves have different key signatures, Graham Percival, 05:00
  • Issue 425 in lilypond: input/regression/spacing-non-adjacent-column2.ly, codesite-noreply, 04:59
  • Re: Regression: spacing-non-adjacent-columns2.ly, Graham Percival, 04:56
  • Issue 424 in lilypond: input/regression/accidental-forced-tie.ly, codesite-noreply, 04:55
  • Re: Regression: accidental-forced-tie.ly, Graham Percival, 04:55
• August 26, 2007
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 19:15
  • Issue 422 in lilypond: beamlets appear to touch, codesite-noreply, 18:34
  • Issue 422 in lilypond: beamlets appear to touch, codesite-noreply, 18:30
  • Issue 423 in lilypond: beamlets appear to touch, codesite-noreply, 18:26
  • Issue 422 in lilypond: beamlets appear to touch, codesite-noreply, 18:22
  • Issue 421 in lilypond: beamlets appear to touch, codesite-noreply, 18:18
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 17:46
  • Issue 391 in lilypond: using relative filepath in \include "foo.ly", codesite-noreply, 17:02
  • Issue 391 in lilypond: using relative filepath in \include "foo.ly", codesite-noreply, 16:58
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 16:54
  • Issue 391 in lilypond: using relative filepath in \include "foo.ly", codesite-noreply, 16:47
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 16:38
  • Re: Starting a Piano Staff with an appoggiatura (acciaccatura)?, Joern Eichler, 16:10
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 16:06
  • Issue 391 in lilypond: using relative filepath in \include "foo.ly", codesite-noreply, 16:00
  • Issue 420 in lilypond: trill spanner tr misaligned, codesite-noreply, 15:56
  • Re: Starting a Piano Staff with an appoggiatura (acciaccatura)?, Kieren MacMillan, 15:42
  • Re: Starting a Piano Staff with an appoggiatura (acciaccatura)?, Valentin Villenave, 15:42
  • Starting a Piano Staff with an appoggiatura (acciaccatura)?, Joern Eichler, 15:25
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 15:19
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 11:11
  • Regression: spacing-non-adjacent-columns2.ly, Christian Hitz, 10:36
  • Regression: accidental-forced-tie.ly, Christian Hitz, 09:22
  • Should slurs really start before the key signature?, arvidgr, 04:35
• August 25, 2007
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 20:00
  • Tie too short after break when staves have different key signatures, Neil Puttock, 19:57
  • Issue 259 in lilypond: collision dynamic cresc, codesite-noreply, 19:38
  • Issue 410 in lilypond: tie too short when clef change at end of system, codesite-noreply, 19:34
  • Issue 259 in lilypond: collision dynamic cresc, codesite-noreply, 19:22
  • Issue 420 in lilypond: trill spanner tr misaligned, codesite-noreply, 19:15
• August 23, 2007
  • Ugly spanner positioning in trill spanner, Neil Puttock, 15:26
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 11:47
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 11:08
  • Re: corrupt collision avoiding when using simultaneous voices, Luc, 10:25
  • Re: corrupt collision avoiding when using simultaneous voices, Mats Bengtsson, 02:58
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 01:15
• August 22, 2007
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 22:41
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 22:27
  • corrupt collision avoiding when using simultaneous voices, Luc, 10:28
• August 21, 2007
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 09:30
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 08:55
  • Re: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, Trevor Bača, 08:42
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 08:41
  • 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, Trevor Bača, 08:21
  • Issue 419 in lilypond: 2.11.30: ... (ly:font-load "aybabtu"): font.scm:175:29: #<unknown port>:138:24: missing close paren, codesite-noreply, 08:20
  • Issue 418 in lilypond: tie & cautionary accidental doesn't properly override following accidental, codesite-noreply, 04:09
  • Issue 416 in lilypond: removing Forbid_line_break_engraver doesn't always work, codesite-noreply, 03:40
  • Re: Forbid_line_break_engraver again, Mats Bengtsson, 03:02
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 01:33
  • Issue 395 in lilypond: Stems too long in case of feathered kneed beams., codesite-noreply, 00:50
  • Issue 404 in lilypond: request: setting the output filename, codesite-noreply, 00:46
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 00:41
  • 13 messages from Google Code, codesite-noreply, 00:37
  • Issue 254 in lilypond: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION), codesite-noreply, 00:33
  • Issue 98 in lilypond: collision bar numbers and StaffGroup, codesite-noreply, 00:29
  • Issue 62 in lilypond: trill not always centered, codesite-noreply, 00:25
  • Re: Rehearsal marks take up extra space when used on full-measure rests, Graham Percival, 00:11
  • Issue 417 in lilypond: Rehearsal marks take up extra space when used on full-measure rests, codesite-noreply, 00:11
  • Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, codesite-noreply, 00:04
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 00:00
• August 20, 2007
  • Issue 414 in lilypond: Hairpin through piano staff change cases explosions, codesite-noreply, 23:56
  • Re: Forbid_line_break_engraver again, Graham Percival, 23:53
  • Issue 416 in lilypond: removing Forbid_line_break_engraver doesn't always work, codesite-noreply, 23:52
  • Re: Break-align-symbol has no effect, Graham Percival, 23:46
  • Issue 413 in lilypond: PNG image is offset an therefore cropped a little, codesite-noreply, 22:48
  • Re: tuplet, tremolo and cross staff, Philippe Raynaud, 16:17
  • Re: programming error: bounds of this piece aren't breakable., karim haddad, 06:37
• August 19, 2007
  • Rehearsal marks take up extra space when used on full-measure rests, Panteck, 16:12
• August 18, 2007
  • Issue 369 in lilypond: \change Staff=foo affects beam too early, codesite-noreply, 21:11
  • Re: Todays git shows #399 again I think, Joe Neeman, 21:10
  • Issue 392 in lilypond: Wrong vim compiler file., codesite-noreply, 21:07
  • Re: Hidden accidental of tied note still takes space in 2.11.19, Joe Neeman, 21:05
  • Issue 414 in lilypond: Hairpin through piano staff change cases explosions, codesite-noreply, 17:51
  • Issue 415 in lilypond: Hidden accidental of tied note still takes space, codesite-noreply, 15:18
  • Re: Hairpin through piano staff change causes explosions, Trevor Bača, 12:40
  • Issue 414 in lilypond: Hairpin through piano staff change cases explosions, codesite-noreply, 12:38
  • Hairpin through piano staff change causes explosions, Trevor Bača, 12:33
  • Issue 414 in lilypond: Hairpin through piano staff change cases explosions, codesite-noreply, 12:32
  • Re: chordmode :13 leaving out 11, Brett Duncan, 01:20
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 01:15
  • Issue 335 in lilypond: extender passes beginning of second node, codesite-noreply, 01:11
  • Issue 331 in lilypond: Lyric extender extends far beyond end of voice, codesite-noreply, 01:07
  • Issue 404 in lilypond: request: setting the output filename, codesite-noreply, 00:55
  • Issue 411 in lilypond: bar numbers too high in pianostaff, codesite-noreply, 00:42
  • Issue 413 in lilypond: PNG image is offset an therefore cropped a little, codesite-noreply, 00:38
  • Issue 305 in lilypond: positioning of hairpins and dynamics, codesite-noreply, 00:34
  • Issue 335 in lilypond: extender passes beginning of second node, codesite-noreply, 00:25
  • Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 00:21
  • Issue 389 in lilypond: \t -> tab in LSR snippets, codesite-noreply, 00:17
  • Issue 393 in lilypond: Line-breaking causes one case of beam insanity, codesite-noreply, 00:13
• August 17, 2007
  • Issue 406 in lilypond: Feathered beams do not work with knees, codesite-noreply, 23:33
  • Issue 408 in lilypond: Melismata at end of line aren't aligned properly, codesite-noreply, 23:29
  • Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, codesite-noreply, 23:20
  • Issue 407 in lilypond: tabStaff cannot handle \partcombine, codesite-noreply, 23:14
  • Issue 411 in lilypond: bar numbers too high in pianostaff, codesite-noreply, 22:24
  • Hidden accidental of tied note still takes space in 2.11.19, Wilbert Berendsen, 05:28
  • Issue 410 in lilypond: tie too short when clef change at end of system, codesite-noreply, 05:17
  • Forbid_line_break_engraver again, Mats Bengtsson, 04:50
  • Todays git shows #399 again I think, Wilbert Berendsen, 03:04
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 02:55
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 02:48
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Joe Neeman, 02:23
  • Re: Break-align-symbol has no effect, Joe Neeman, 02:15
• August 16, 2007
  • Issue 409 in lilypond: collision tie and time signature, codesite-noreply, 23:26
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 21:37
  • Issue 408 in lilypond: Melismata at end of line aren't aligned properly, codesite-noreply, 21:33
  • Issue 410 in lilypond: tie too short when clef change at end of system, codesite-noreply, 21:29
  • Issue 411 in lilypond: bar numbers too high in pianostaff, codesite-noreply, 21:25
  • Issue 412 in lilypond: bar number positioning influenced by clef change at end of previous system, codesite-noreply, 21:19
  • Issue 409 in lilypond: collision time and time signature, codesite-noreply, 20:47
  • Issue 410 in lilypond: tie too short when clef change at end of system, codesite-noreply, 20:43
  • Issue 413 in lilypond: PNG image is offset an therefore cropped a little, codesite-noreply, 20:12
  • abc2ly: Several problems with alternatives, glambrouin, 15:18
  • Re: chordmode :13 leaving out 11, Rick Hansen (aka RickH), 12:51
• August 15, 2007
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 18:40
  • Re[2]: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 18:19
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 18:03
  • Re: programming error: bounds of this piece aren't breakable., Mats Bengtsson, 15:00
  • programming error: bounds of this piece aren't breakable., Karim . Haddad, 13:47
  • Re: Strange warning - is this a bug?, Graham Percival, 03:13
• August 14, 2007
  • Re: Tie / Time Signature collisions, Valentin Villenave, 18:13
  • Re: Tie / Time Signature collisions, Graham Percival, 17:23
  • Re: Melismata at end of line aren't aligned properly, Graham Percival, 17:21
  • Re: Editor Support Docs, Graham Percival, 17:18
  • Re: DynamicTextSpanner - 3 bugs?, Graham Percival, 17:10
  • Re: Feathered beams do not work with knees, Graham Percival, 15:23
  • Re: Beam_engraver doesn't seem to handle Clef collisions, Valentin Villenave, 13:06
  • Re: Feathered beams do not work with knees, Han-Wen Nienhuys, 10:40
  • Re: tuplet, tremolo and cross staff, Mats Bengtsson, 07:49
  • Re: chordmode :13 leaving out 11, Graham Percival, 06:02
  • Issue 407 in lilypond: tabStaff cannot handle \partcombine, codesite-noreply, 06:00
  • Re: tuplet, tremolo and cross staff, Graham Percival, 05:59
  • Re: TabStaff and partcombine do not seem to work together, Graham Percival, 05:57
  • Issue 333 in lilypond: lyrics delayed by one note with \partial and \override VerticalAxisGroup, codesite-noreply, 05:56
  • Issue 406 in lilypond: Feathered beams do not work with knees, codesite-noreply, 05:52
  • Re: Feathered beams do not work with knees, Graham Percival, 05:51
  • Re: Cross-staff beaming in PianoStaff fails when combined with slur, Graham Percival, 05:48
  • Issue 369 in lilypond: \change Staff=foo affects beam too early, codesite-noreply, 05:48
  • Re: Beam_engraver doesn't seem to handle Clef collisions, Graham Percival, 05:45
  • Re: Tuplet bracket sometimes not printed, Graham Percival, 05:38
  • Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, codesite-noreply, 05:38
  • Issue 404 in lilypond: request: setting the output filename, codesite-noreply, 05:25
  • Re: misplaced TextSpanner-text when bar-engraver is removed and line breaks, Graham Percival, 05:23
  • Issue 401 in lilypond: misplaced textSpanner when Bar_engraver is removed, codesite-noreply, 05:20
  • Re: LilyPond for OS X: Intel download shows as PowerPC, Graham Percival, 05:14
  • Issue 403 in lilypond: osx builds report creation date of March 23, 2006, codesite-noreply, 05:14
  • Issue 402 in lilypond: osx intel app lists itself as "ppc", codesite-noreply, 05:10
  • Re: Freebsd-64 = dead link, Jan Nieuwenhuizen, 02:57
  • Re: Break-align-symbol has no effect, Graham Percival, 02:49
  • Re: Break-align-symbol has no effect, Joe Neeman, 01:45
• August 13, 2007
  • Re: Break-align-symbol has no effect, Neil Puttock, 18:41
  • Re: Break-align-symbol has no effect, Joe Neeman, 18:12
  • Re: Cross-staff beaming in PianoStaff fails when combined with slur, Neil Puttock, 16:37
  • Break-align-symbol has no effect, Neil Puttock, 16:25
  • Freebsd-64 = dead link, Jean-Charles Malahieude, 15:32
  • Re: Distance between staves in PianoStaff not fixed, Mats Bengtsson, 02:30
• August 12, 2007
  • Distance between staves in PianoStaff not fixed, Neil Puttock, 17:00
  • Cross-staff beaming in PianoStaff fails when combined with slur, Neil Puttock, 16:25
  • RE: DynamicTextSpanner - 3 bugs?, Fairchild, 07:46
  • Re: DynamicTextSpanner - 3 bugs?, Joe Neeman, 01:59
• August 11, 2007
  • FW: Problem: ragged-last = ##t gives cramped last line, Fairchild, 20:49
  • DynamicTextSpanner - 3 bugs?, Fairchild, 15:05
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 04:50
• August 10, 2007
  • LilyPond for OS X: Intel download shows as PowerPC, Brian, 23:30
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Han-Wen Nienhuys, 21:59
  • Editor Support Docs, Zack Charter, 20:45
• August 08, 2007
  • Re: Lilymidi 2.11.28 on Mac OS X 10.4.10, Hans Aberg, 15:01
  • Lilymidi 2.11.28 on Mac OS X 10.4.10, Hans Aberg, 08:39
• August 07, 2007
  • Re: Strange beams subdivision when manually beaming over a rest, Graham Percival, 19:36
  • Melismata at end of line aren't aligned properly, Peter Budny, 17:35
  • bug or limitation ?, karim haddad, 12:34
• August 06, 2007
  • Re: kneed spacing too tight, as of git 4 august (recently introduced regression), Joe Neeman, 18:03
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 08:10
  • kneed spacing too tight, as of git 4 august (recently introduced regression), Wilbert Berendsen, 02:34
  • Issue 62 in lilypond: trill not always centered, codesite-noreply, 02:30
• August 05, 2007
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 22:54
  • Re: Strange beams subdivision when manually beaming over a rest, Valentin Villenave, 21:08
  • Re: Strange beams subdivision when manually beaming over a rest, Valentin Villenave, 21:05
  • Re: Strange beams subdivision when manually beaming over a rest, Graham Percival, 19:56
  • Re: Strange beams subdivision when manually beaming over a rest, Valentin Villenave, 19:24
  • Re: Strange warning - is this a bug?, Mats Bengtsson, 17:22
  • RE: Strange beams subdivision when manually beaming over a rest, Fairchild, 17:04
  • Re: Lyrics skip first note when mixed with formatting, Mats Bengtsson, 16:59
• August 04, 2007
  • Re: Beam_engraver doesn't seem to handle Clef collisions, Valentin Villenave, 21:01
  • Tie / Time Signature collisions, Valentin Villenave, 20:57
  • Re: Lilypond, Graham Percival, 19:45
  • Lilypond, Raquel, 19:31
  • Issue 401 in lilypond: misplaced textSpanner when Bar_engraver is removed, codesite-noreply, 17:48
  • Re: misplaced TextSpanner-text when bar-engraver is removed and line breaks, Graham Percival, 17:48
  • Issue 400 in lilypond: collision clef and beam, codesite-noreply, 17:43
  • Re: Beam_engraver doesn't seem to handle Clef collisions, Graham Percival, 17:43
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 17:26
  • Re: Strange beams subdivision when manually beaming over a rest, Valentin Villenave, 06:10
  • Re: Strange beams subdivision when manually beaming over a rest, Graham Percival, 04:56
  • Re: install problems, Graham Percival, 04:55
  • install problems, Mary Evans, 04:50
• August 03, 2007
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 20:08
  • Issue 357 in lilypond: slurs with \slurDashed don't count towards skyline, codesite-noreply, 20:04
  • Strange beams subdivision when manually beaming over a rest, Valentin Villenave, 13:07
  • misplaced TextSpanner-text when bar-engraver is removed and line breaks, Luc, 10:27
• August 02, 2007
  • Beam_engraver doesn't seem to handle Clef collisions, Valentin Villenave, 18:30
  • Re: OttavaBracket dash-period bug?, Valentin Villenave, 18:15
  • Re: bug? clef takes too much space when changing both staff and clef in some circumstances, Wilbert Berendsen, 14:15
• August 01, 2007
  • Re: Tuplet bracket sometimes not printed, Trevor Bača, 22:46
  • Re: Tie_engraver doesn't handle TrillPitchGroup collisions, Valentin Villenave, 21:40
  • Re: bug? clef takes too much space when changing both staff and clef in some circumstances, Graham Percival, 21:38
  • Issue 399 in lilypond: clef can take too much space when changing staffs in piano music, codesite-noreply, 21:38
  • Re: collision at end of system with clef and change staff, Graham Percival, 21:34
  • Issue 398 in lilypond: collision clef / stem with changing piano staff, codesite-noreply, 21:34
  • Re: lyrics in volta confuses Bar_engraver, Graham Percival, 21:29
  • Issue 333 in lilypond: lyrics delayed by one note with \partial and \override VerticalAxisGroup, codesite-noreply, 21:28
  • Re: Lyrics skip first note when mixed with formatting, Graham Percival, 21:27
  • Re: Tie_engraver doesn't handle TrillPitchGroup collisions, Graham Percival, 21:18
  • Issue 397 in lilypond: collision pitchedTrill and tie, codesite-noreply, 21:18
  • Re: Tuplet bracket sometimes not printed, Graham Percival, 21:15

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc