Updates:
Labels: Priority-Postponed
Comment #2 on issue 1239 by Carl.D.Sorensen: [PATCH] Make
pure-print-callbacks public (issue1983047)
http://code.google.com/p/lilypond/issues/detail?id=1239
Although the patch works, the idea seems to be not yet ready for inclusion
in the code base.
Users adding a pure print callback can trigger infinite loops that produce
no error messages.
Until we can get a clear definition of how to avoid this problem, we don't
really want to make pure-print-callbacks publicly accessible.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond