On 2009-10-27, Joe Neeman wrote: > On Tue, 2009-10-27 at 01:54 -0700, 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? > > It should just be a matter of setting breakable to ##t by default in the > Beam grob.
Oops, thanks for catching that. However, I found a comment in ly/declarations-init.ly: %% FIXME %% should also set \override Beam #'breakable, but how to do it %% "portably"? (ie. also working with lyric sections) %% %% try \once \override Score.Beam #'breakable = ##t A real solution sounds more complicated, in other words. -Patrick _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
