Am 13.01.2016 um 10:08 schrieb Mark Knoop: > At 22:57 on 12 Jan 2016, Urs Liska wrote: >> Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >>>> What should the behavior of the *last* one be here? >>> No beams over the rest. >> Well, default behaviour is to break the beam at all rests here (see >> attached). > Not sure if this is relevant to your current work on this, but it would > be great to have a global override to create beams over rests WITHOUT > having to manually enter them. The implementation would need quite some > thought as to the kind of parameters needed, e.g. maximum-rest-value, > minimum-beam-count, etc. >
This is conceptually relevant but practically a different issue. Not only because of the mentioned complexity (which I'd rather *not* touch in addition to everything else) but also because it's a different place in the code as well. The code I am working on takes a given beam for granted. Deciding what to beam automatically has already been done by that time. And for the beaming pattern it doesn't make a difference whether the beam has been created manually or automatically. So I suggest you post a feature request to bug-lilypond. Urs _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
