Am 15.04.2017 um 13:54 schrieb Son_V: > Hi all, Lilypond (using \override Score.BarNumber #'break-visibility = #'#(#t > #t #t) ) writes at the end of a score, the number of the next beam, that is > written at the beginning of the subsequent score; and it writes at the end > of the last score the number that should be at the beginning of an > inexistent next score. > Now I don't have at hand "Beyond bars", so I can't say if it's a correct > behaviour or not. But it seems strange to me IMHO.
It’s strange indeed, but it’s also exactly what you asked for by setting break-visibility to #'#(#t #t #t) or it’s shortcut #all-visible. Try \override Score.BarNumber.break-visibility = #'#(#f #t #t) or the shortcut \override Score.BarNumber.break-visibility = #end-of-line-invisible instead. And concerning Kieren’s comment about patches: This is not LilyPond’s mistake. And if you turn off the very last bar number even if bar numbers are set to #all-visible that would be very confusing. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
