Graham Percival wrote Sunday, March 29, 2009 4:12 AM
On Sat, Mar 28, 2009 at 08:38:08PM +0000, Anthony W. Youngman
wrote:
In message <3cbf99092d5f4e77a0cae01edf7be...@trevorlaptop>,
Trevor
Daniels <t.dani...@treda.co.uk> writes
You'll be pleased to know the revert will not be required
at all in 2.13.1 to obtain this beaming.
It works fine now. But (as others have mentioned) why not in
2.12.3?
imho it's a bug, and as such ought to be fixed.
Due to limited resources, we're finished with 2.12. The next
stable version, 2.14, will probably be out in 4-6 months.
If you don't like this, then please volunteer to spend 10 hours a
week backporting things to 2.12, plus something like 100 hours
learning git, the lilypond build process, testing lilypond builds,
etc.
Also, this change is just one of many I made to the auto-beaming
defaults in the same commit. These have the potential to
change (that's a euphemism for screw-up) the beaming of
existing scores. I do not intend to apply such a change to
a stable release before it has been properly evaluated and
tested in a development release; nor should you. Especially
when there is a simple documented work-around.
Trevor
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
