Re: Lyric extender

[Shane Brandes]

Lilypond version 2.17.95 sorry about version the omission.
I solved the problem with this unpleasant kludge:
\once\override TextScript.extra-offset = #'(4.2 . -2.5) <g bes es>1
_"___________________"

but if anyone comes up with something more effective I will implement
it. The melismaBusy set unset does not work since a melisma needs more
than a single note to work.

I agree with Kieren.

Thanks,
Shane

On Mon, Dec 16, 2013 at 1:53 PM, Kieren MacMillan
<address@hidden> wrote:
> Hi Trevor (et al.),
>
>> You don't say what release you are using, but if it's a fairly
>> recent release 17 this may help you:
>> http://www.lilypond.org/doc/v2.17/Documentation/notation/techniques-specific-to-lyrics#polyphony-with-shared-lyrics
>
> This is nice!
>
> But ultimately it shows that we still need easier and more intuitive 
> methods/interfaces… Imagine, if you will, something like:
>
>     Here’s my lyr — ic, __4 in which ex — ten — ders have a dur — a — tion! 
> __2*3
>
> I am totally oblivious to how this might work/not/interfere/crash, but it’s 
> far better (in my opinion) than having to add a whole separate context for 
> something as simple as controlling the length of a lyric extender.
>
> Cheers,
> Kieren.