On 2009-10-27, Patrick McCarty wrote: > On 2009-09-27, Werner LEMBERG wrote: > > > > >> What's the reason that line breaks are by default forbidden if > > >> there is a broken beam crossing the bar line, and that you have to > > >> set the `breakable' flag manually to override it? > > >> > > >> BTW, it is very unpleasant that lilypond doesn't emit any kind of > > >> warning if it produces an overlong staff caused by that issue. It > > >> silently accumulates unbreakable bars and happily walks out of the > > >> right margin. I would consider this behaviour a bug. > > > > > > +1. > > > > > > (I've always felt this way, too.) > > > > Then let's drop the IMHO unfounded limitation of not breaking at beams > > crossing a barline. > > This would just require (I think) a revert of Han-Wen's commit > a6f65c52e2a20cd64067da45945e485d74ac3105. > > See the attached patch. What do you think?
Hmm. I'll take that back. There were more changes made in that commit, but I don't understand the effect of the other changes, e.g. moving the typeset_beam() call from stop_translation_timestep() to process_music(). -Patrick _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
