lilypond-bug

2011-04-01 - 2011-05-01 (559 messages)

2011-03-01 - 2011-04-01 (543 messages)

2011-02-01 - 2011-03-01 (588 messages)

 Next  Last 

  1. 2011-03-31  [2] Issue 1585 in lilypond: LilyPond segfaults on beams with headless stenci lilypond-bug lilypond
  2. 2011-03-31  [3] Issue 1587 in lilypond: midi2ly --key option only reaches first staff    lilypond-bug lilypond
  3. 2011-03-31  [5] Re: Issue 400 in lilypond: collision clef and beam                       lilypond-bug lilypond
  4. 2011-03-31  [4] Re: Issue 76 in lilypond: beams should not collide with accidentals      lilypond-bug lilypond
  5. 2011-03-31  [1] Re: Issue 795 in lilypond: Beams do not take grace notes into account    lilypond-bug lilypond
  6. 2011-03-31  [2] Issue 1586 in lilypond: midi cresc happens instantly                     lilypond-bug lilypond
  7. 2011-03-31  [2] Fw: Critical bug of midi output                                          lilypond-bug Graham Percival 
  8. 2011-03-31  [5] Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieW lilypond-bug lilypond
  9. 2011-03-31  [5] Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note la lilypond-bug lilypond
 10. 2011-03-31  [1] header items: use #f or ##f ?                                            lilypond-bug -Eluze 
 11. 2011-03-31  [2] stemlength                                                               lilypond-bug Phil Holmes 
 12. 2011-03-31  [2] Issue 1584 in lilypond: removing parser DIGIT rule                       lilypond-bug lilypond
 13. 2011-03-31  [3] Re: Issue 688 in lilypond: grace notes may add an hyphen at the beginnin lilypond-bug lilypond
 14. 2011-03-31  [3] Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion     lilypond-bug lilypond
 15. 2011-03-31  [3] Issue 1549 in lilypond: midi2ly should output rests by default           lilypond-bug lilypond
 16. 2011-03-31  [4] Issue 1573 in lilypond: Downstem 64th and 128th flag touchup             lilypond-bug lilypond
 17. 2011-03-31  [3] Issue 1575 in lilypond: midi2ly --duration-quant=16 fails to display fir lilypond-bug lilypond
 18. 2011-03-31  [4] Issue 1580 in lilypond: midi2ly creates invalid LilyPond input for a sta lilypond-bug lilypond
 19. 2011-03-31  [3] Issue 1578 in lilypond: Enhancement: Allows glissandi to be continuous a lilypond-bug lilypond
 20. 2011-03-31  [9] Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing        lilypond-bug lilypond
 21. 2011-03-31  [5] Re: Issue 1504 in lilypond: Feathered beams reset at line break          lilypond-bug lilypond
 22. 2011-03-30  [2] horizontal spacing: note too close to barline when time signature change lilypond-bug Ralph Palmer 
 23. 2011-03-30  [1] Issue 1583 in lilypond: horizontal spacing: note too close to barline wh lilypond-bug lilypond
 24. 2011-03-30  [4] Issue 1579 in lilypond: Overextended lyrics extenders                    lilypond-bug lilypond
 25. 2011-03-30  [2] dynamic placement problem with slurred notes                             lilypond-bug Dmytro O. Redchuk 
 26. 2011-03-28  [1] Issue 1582 in lilypond: flag variants patch                              lilypond-bug lilypond
 27. 2011-03-28  [1] Re: \pitchedTrill causes warning when used with tie                      lilypond-bug Neil Puttock 
 28. 2011-03-28  [1] Issue 1581 in lilypond: Pitched trill between tied notes causes `untermi lilypond-bug lilypond
 29. 2011-03-28  [2] Issue 1574 in lilypond: DOC: Need updated/expanded documentation of perc lilypond-bug lilypond
 30. 2011-03-28  [4] Re: Issue 1530 in lilypond: [PATCH] Fret diagram fixes (Issue 4176056)   lilypond-bug lilypond

 Next  Last