Re: warning: no feasible beam position

[Han-Wen Nienhuys]

Stephen wrote:
I never followed up with this properly, but now I can report that the
> bug dropped out with version 2.6.4. Does anyone happed to know how the 
> bug was fixed?


I guess it was

2005-08-04  Han-Wen Nienhuys  <address@hidden>

        * lily/beam.cc (shift_region_to_valid): prevent division by
        zero. Fixes beams across line breaks with 1 stem after the break.


> > I am rather astonished that Lily handles this piece of notation so well.
>
> My goal is to test Lilyponds limitations by trying to notate something 
> really challenging. I am gratified that you are astonish since that is 
> the point (not to astonish you but to demonstrate what Lilypond is 
> capable of.). What is fascinating to me is that Lilypond is capable of 
> more than its creators and developers are aware of. In this way it 

No, it's because doing music notation well means a hundred-odd small 
formatting details correctly. Usually, we mess up on one of those 
hundred details, and the page looks crap. This page doesn't show any of 
those major faults. Then, all of a sudden, the output looks glorious.

> corresponds to a computer language since it also is extensible and is 
> capable of more than its creators can anticipate. And like a computer 
> language Lilypond has an internal logic that sometimes allows the user 
> to give it compands that it responds to in a predictable way that its 
> creators do not anticipate.


> Unfortunately, Lilypond may be moving away from this design philosophy now.

Why?

> > BTW, I've been thinking about a
> >
> >   \override Slur #'details #'edge-attraction-factor = 21
> >
> > syntax. Perhaps you'd be interested in sponsoring it?

I've actually added this to the 2.7 series, because I needed it for 
other purposes.

--
 Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen