Janek Warchoł writes: > i suppose relevant issue is here > http://code.google.com/p/lilypond/issues/detail?id=1948
Interesting. So instead of FIXING that bug, a new bug was introduced by removing code. Great. Also no trail was left in Git, which leaves the risk of someone restarting that cycle from scratch: Add lilypond to path, fix some more bugs, finally remove it again etc, etc. Jan -- Jan Nieuwenhuizen <[email protected]> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
