Tim McNamara wrote:
>
>
> Also, IMHO the syntax for placing a coda, a segno, etc. ought to be as
> elegant and simple as possible (e.g., \coda or \segno instead of \mark
> \markup { \musicglyph #"scripts.coda" } or \mark \markup { \musicglyph
> #"scripts.segno" } Less typing means fewer errors ).
>
> Thanks for your questions and the suggestion, I will check that out.
>
> Tim
>
Hi Tim,
to avoid unnecessary typing and needless errors define more variables and
macros.
I don't want to miss lilypond-default-behaviour, but you can change it:
See http://lsr.dsi.unimi.it/LSR/Item?id=736 LSR-Snippet 736
Example:
\version "2.14.2"
Line = { \repeat unfold 4 {s1} \break }
Coda = \mark \markup { \musicglyph #"scripts.coda" }
Segno = \mark \markup { \musicglyph #"scripts.segno" }
one = {
\relative c'' {
\Line \Coda
\Line \Coda
\Line
}
}
two = {
\relative c' {
\Line \Segno
\Line \Segno
\Line
}
}
\score {
\relative c'
<<
\new Staff {
<<
\new Voice \with {
\consists Mark_engraver
\consists "Staff_collecting_engraver"
\override RehearsalMark #'break-visibility = #'#(#t #t #f)
\override RehearsalMark #'color = #blue
}
{\voiceOne \one}
\new Voice \with {
\consists Mark_engraver
\consists "Staff_collecting_engraver"
%\override RehearsalMark #'direction = #DOWN
}
{\voiceFour \two}
>>
}
>>
\layout {
\context {
\Score
\remove "Mark_engraver"
\remove "Staff_collecting_engraver"
}
}
}
%or
\relative c'' {
\override Score.RehearsalMark #'break-visibility = #'#(#t #t #f)
\Line \Coda
\Line \Coda
\Line
}
HTH,
Harm
--
View this message in context:
http://old.nabble.com/Overriding-shifting-of-coda-when-%5Cbreak-is-used--tp32208915p32210199.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
