Richard Shann <[email protected]> writes: > On Fri, 2015-09-04 at 20:20 +0200, David Kastrup wrote: >> Richard Shann <[email protected]> writes: >> >> > Please correct me if I am wrong, but at the moment I don't know how a >> > user can place a something at the top of a LilyPond file that will >> > result in a particular beaming rule being applied whenever they use a >> > particular time signature. >> >> \layout { >> \overrideTimeSignatureSettings ... >> } >> > > Thank you, that was the bit that is missing from the page you referred > to. I suggest that this text from that page: > > Alternatively, the default values of all these time-signature-based > variables, including baseMoment and beamExceptions, can be set together. > The values can be set independently for several different time > signatures. The new values take effect when a subsequent \time command > with the same value of the time signature is executed: > > > should become > > Alternatively, the default values of all these time-signature-based > variables, including baseMoment and beamExceptions, can be set together. > The values can be set independently for several different time > signatures. This can be done in a \layout {} block when it affects all > the passages with the specified time signature in the score block it is > placed in (or all the score blocks if the layout block is at the top > level). Or if placed in the music, the new values take effect when a > subsequent \time command with the same value of the time signature is > executed and affects only the staff in which it is placed:
But that's the same with every single context property setting command. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
