Werner LEMBERG <wl <at> gnu.org> writes: > >> it is not easy to decide whether the bar number should be moved to > >> the non-ossia staff. > > > > I see no application where it would make sense to keep it above. > > Here's the only solution (already in the notation reference) which > works correctly
The temporary staff is more natural, but sometimes we need to use a continuous staff with \startStaff \stopStaff in order to convince LilyPond that it goes on the same line http://code.google.com/p/lilypond/issues/detail?id=1449 For the original example, \override Score.BarNumber #'after-line-breaking = ##f The down-side is that the BarNumber is not properly counted for page-spacing (only a problem if someone overrides the bar-number to print something very large). It would be good to replace 4cabd2305eda952e2d29e4a04e75e1cfb499257a with a different method of including in the page-spacing calculation those grobs created in contexts like StaffGroup or Score, and thus having parents that are System or StaffGrouper rather than the usual VerticalAxisGroup. http://code.google.com/p/lilypond/issues/detail?id=2199 _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
