> slurs and dynamic texts are involved in collision resolution; check > the avoid-slur properties on DynamicText and DynamicLineSpanner.
Indeed, this did the trick: f1 \once \override DynamicText #'X-offset = #'-5.0 \once \override DynamicLineSpanner #'Y-offset = #'-5.0 \once \override DynamicLineSpanner #'outside-staff-priority = ##f \once \override DynamicLineSpanner #'avoid-slur = ##f c1\ff( | f1) | Thanks for the help. Quite complicated IMHO... However, I get a warning Ignoring grob for slur. avoid-slur not set? which isn't appropriate in this case since I explicitly override the property. Can you disable it (at least in such situations)? I wonder whether it makes sense to introduce a property, say, `offset', which is the same as `extra-offset' but which actually takes part in formatting. Due to the central role of X- and Y-offset it's probably a bad idea to directly manipulate them. We would have a workflow similar to this: . compute X-offset and Y-offset of the grob as usual . apply `offset' . finish formatting . apply `extra-offset' The `offset' property would be quite convenient (and predictable) for the end user. However, my point of view is quite naive since I lack knowledge of lilypond internals. Werner _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel