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?

Thanks,
Patrick
>From 8d3179adcb90dcdcd3d0d6f5978083cb3ff4c38b Mon Sep 17 00:00:00 2001
From: Patrick McCarty <pnor...@gmail.com>
Date: Tue, 27 Oct 2009 01:48:10 -0700
Subject: [PATCH] At line breaks, break beams by default

---
 scm/define-grobs.scm |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/scm/define-grobs.scm b/scm/define-grobs.scm
index e311c3b..22ab1d1 100644
--- a/scm/define-grobs.scm
+++ b/scm/define-grobs.scm
@@ -370,8 +370,7 @@
                 (object-callbacks . ((normal-stems . 
,ly:beam::calc-normal-stems)))
                 (interfaces . (beam-interface
                                font-interface
-                               staff-symbol-referencer-interface
-                               unbreakable-spanner-interface))))))
+                               staff-symbol-referencer-interface))))))
 
     (BendAfter
      . (
-- 
1.6.5.2

_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to