Am Sonntag, 5. Juni 2005 21:09 schrieb Graham Percival: > Well, yes. We can't figure out what went wrong without an > input file.
Nevermind, I figured it out myself. You were right, I was actually doing something fancy. It was a bar-number trick that I took from one of the example files: \override Score.BarNumber #'break-visibility = #end-of-line-invisible \set Score.barNumberVisibility = #(every-nth-bar-number-visible 5) \override Score.BarNumber #'print-function = #(make-stencil-boxer 0.1 0.25 0.25 Text_interface::print) \override Score.BarNumber #'font-size = #1 \override Score.BarNumber #'extra-offset = #'(1 . 1) When I deleted the second "0.25" argument it worked. As for the one-line-staff bug: Any news? Did you reproduce it? Best regards, Robert _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
