Urs Liska wrote Tuesday, March 15, 2016 8:44 AM > I would like to ask for your opinion on the matter of switching beam > subdivisions on or off by default. > > I would strongly suggest to switch the default setting so that > subdivideBeams is set to #t by default. I know that will affect existing > scores, but the more I think of it the more I think this should be the > default behaviour (after all, it's simple to switch it off). > > Page 156 of "Behind Bars" clearly suggests to use beam subdivisions. > It's not stated as mandatory, but neither as purely optional or a matter > of taste. First she claims "Groups of notes are clearest to read when > ..." followed by "In ... separate inner beams into ...". Followed then > by a negative example of "not recommended" beaming - which shows > LilyPond's default. > > When faced with the attached example Elaine Gould states: "YES > absolutely, (c) as default". > > So, before integrating that into my code I would collect opinions. Are > there any strong (and reasoned) objections against changing the default > here?
I agree we should switch the default, as long as it is clearly stated in Changes, perhaps under a heading New Default(s). Trevor _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
