Re: Issue 1702 in lilypond: Unaesthetic beam slope

[lilypond]

Updates:
        Status: Invalid

Comment #1 on issue 1702 by address@hidden: Unaesthetic beam slope
http://code.google.com/p/lilypond/issues/detail?id=1702

The staff-separation was intentionally reduced for 2.14.
LilyPond would normally give the beamed sets a uniform stem direction,
but user input \stemUp changed the stem direction mid-beam, forcing a kneed  
beam.
LilyPond gave a warning that there is not enough room to make a nice beam.
If the e is lowered, then LilyPond spreads the staves further apart rather  
than increasing the beam slope any further.

To this point, current behavior seems the best choice for "desired  
behavior";
that is, LilyPond gave Xavier what he asked for.

Phil noted the collision between beam and accidental, which is an aspect of  
the collision-tolerance of cross staff things, recorded issue 36 or issue  
439.

The change to Lilypond, that made this particular input become ugly, was  
the reduced spacing between staves which was intentional, so I'm marking  
this as Invalid.