On 14 août 2012, at 08:37, Werner LEMBERG wrote:
>
>> Had a chance to look into it.
>
> Thanks.
>
Hey Werner,
I'll explain more below.
>> The too-closeness is registering, so the issue is either one of:
>>
>> 1) The details list for slurs needs different values.
Try stuff like
\override S
> Had a chance to look into it.
Thanks.
> The too-closeness is registering, so the issue is either one of:
>
> 1) The details list for slurs needs different values.
>
> 2) Not enough potential slurs are being generated and thus there is
>no candidate that is far enough away from the tie.
>
On 12 août 2012, at 22:05, Werner LEMBERG wrote:
>
>> Odd...I'll look into it.
>
> Thanks!
>
>
>Werner
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hey Werner,
Had a c
> Odd...I'll look into it.
Thanks!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 12 août 2012, at 16:31, Werner LEMBERG wrote:
>
> [lilypond commit 1dedaf12]
>
>
> Mike,
>
>
> is the problem `start and end points of slurs and ties don't fall
> together' supposed to be fixed? This snippet
>
>
> \version "2.17.0"
>
> \paper {
>ragged-right = ##f
> }
>
> \re
[lilypond commit 1dedaf12]
Mike,
is the problem `start and end points of slurs and ties don't fall
together' supposed to be fixed? This snippet
\version "2.17.0"
\paper {
ragged-right = ##f
}
\relative c' {
\time 5/4 g'2.( ~ g8 a4. ~ |
a1) r4
}
still exhibits a clas
