Re: Slur goes way too high in this passage

[Keith OHara]

ryanmichaelmcclure <ryanmichaelmcclure <at> gmail.com> writes:

> That's the best part about Lilypond,
>       isn't it? :)
>       I've seen this page before. I'll have to take a stab at it
>       sometime. I'm heading to bed right now, and I'll work on this
>       music tomorrow at some point. I'll have to see what I can do with
>       2.16.2...and, possibly install 2.17 as well.
>       Thank you so much for your help!
>       -Ryan McClure
>       On 10/08/2013 12:02 AM, SoundsFromSound [via Lilypond] wrote:
> 
>      In LilyPond, there is always something you can do to
>       workaround pretty much anything. :)
>       
>       Have you looked into this? http://lilypond.org/doc/v2.17/
Documentation/notation/modifying-shapes#modifying-ties-and-slurs
>       It's not your only alternative, however, it is very powerful in
>       certain situations.
>

Probably Ben was meant the \shape function in the documentation
link above.   This function *is* in version 2.16
<http://lilypond.org/doc/v2.16/Documentation/changes/
new-features-in-2_002e16-since-2_002e14>
but it got caught up in some syntax changes so its documentation
did not make it into the main version 2.16 documentation.

You can also just tell LilyPond where you want the endpoints
  c-\tweak #'positions #'(4 . 4)  (
which stops her from trying to reach down to the ending note.

The occasional huge slur is a listed bug
 http://code.google.com/p/lilypond/issues/detail?id=163
but the project thought it was fixed.  It seems it is not.