Jump to content

Positioning text markups inside slurs: Difference between revisions

From LilyPond wiki
m Replace version="2.24.0" with version="2.24" now that the LilyWiki extension supports auto-selecting the latest release in a stable series
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Text markups need to have the <code>outside-staff-priority</code> property set to false in order to be printed inside slurs.
Text markups need to have the <code>outside-staff-priority</code> property set to <code>#f</code> in order to be printed inside slurs.


<lilypond version="2.24">
<lilypond version="2.24">
Line 9: Line 9:
</lilypond>
</lilypond>


[[Category:Expressive marks]]
[[Category:Expressive marks]]
[[Category:Expressive marks]]
[[Category:Editorial annotations]]
[[Category:Editorial annotations]]
[[Category:Tweaks and overrides]]
[[Category:Tweaks and overrides]]
[[Category:Included in the official documentation]]
[[Category:Included in the official documentation]]
[[Category:Snippet]]

Latest revision as of 14:50, 3 December 2025

Text markups need to have the outside-staff-priority property set to #f in order to be printed inside slurs.

\version "2.24"

\relative c'' {
  \override TextScript.avoid-slur = #'inside
  \override TextScript.outside-staff-priority = ##f
  c2(^\markup { \halign #-10 \natural } d4.) c8
}