Simon Albrecht <[email protected]> writes: > Am 31.08.2015 um 14:35 schrieb David Kastrup: >> Martin Tarenskeen <[email protected]> writes: >> >>> On Mon, 31 Aug 2015, Phil Holmes wrote: >>>>> \override Slur.outside-staff-priority = #500 >>>> >>>> I would say so. you might like to add this to the bottom of your example: >>>> >>>> \break >>>> \override Script.outside-staff-priority = #1000 >>> Yes, that looks strange and bad. But maybe not quite fair to use a >>> second override without using \revert to undo the first >>> override. That's asking for trouble. >> Uh, no it isn't? For one thing, only the topmost override is ever >> consulted. For another, \override by itself _always_ reverts one >> preceding override (if present in the context at question) before >> applying its own one. If you want to have some override only >> temporarily active, you need to use \temporary \override in order to >> _not_ revert any previously existing override but have it reappear when >> you \revert your own override. >> >>> When use a \revert before adding your example, the result looks a >>> little less strange. >> I should be surprised. > > Well, the two overrides are unrelated since they point to different > grobs.
Oh. Uhm. In that case, of course both can have a combined effect and reverting either one may make a difference. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
