Hi list,
is there a reason why \germanChords raises accidentals higher than in
other cases? In the past few years I’ve read now several users
complaining about that.
Shouldn’t we remove line 92 (and a closing parenthesis) from
scm/chord-name.scm?
Cheers,
Malte
Hi list,
The function alteration->text-accidental-markup (l. 33ff. in
scm/chord-name.scm) seems to ignore current font size while raising the
accidental:
%%
\version "2.19.82"
\markup \concat { E #(alteration->text-accidental-markup FLAT) }
\markup \concat { E
Thomas Morley writes:
> 2018-07-01 23:07 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> 2018-07-01 21:13 GMT+02:00 David Kastrup :
>>>
Perhaps try running under a debugger and setting a breakpoint on
::warning (or so)? Then make a traceback when the warning is reached
Hi,
the code below returns
programming error: no solution found for Bezier intersection
for 2.19.82 as well as for current master. 2.18.2 is ok.
\version "2.19.82"
oneUp = \relative c' {
%\time 3/4
\voiceOne
1
q
q
q
q
r8
\times 2/3 { 16 q q }
q8 q q r8
r8
q8 q8 q q r8
Colin Campbell writes:
> On 2018-07-01 11:47 AM, Thomas Morley wrote:
>> Hi,
>>
>> the code below returns
>> programming error: no solution found for Bezier intersection
>> for 2.19.82 as well as for current master. 2.18.2 is ok.
>>
>>
>> It's a heavily boiled down version of the original
2018-07-01 19:47 GMT+02:00 Thomas Morley :
> Hi,
>
> the code below returns
> programming error: no solution found for Bezier intersection
> for 2.19.82 as well as for current master. 2.18.2 is ok.
>
> \version "2.19.82"
I was wrong with 2.18.2.
At least the stripped down code errors for 2.18. as
On 2018-07-01 11:47 AM, Thomas Morley wrote:
Hi,
the code below returns
programming error: no solution found for Bezier intersection
for 2.19.82 as well as for current master. 2.18.2 is ok.
It's a heavily boiled down version of the original file (thus the
strange octaves).
Though I'm not
2018-07-01 21:13 GMT+02:00 David Kastrup :
> Colin Campbell writes:
>
>> On 2018-07-01 11:47 AM, Thomas Morley wrote:
>>> Hi,
>>>
>>> the code below returns
>>> programming error: no solution found for Bezier intersection
>>> for 2.19.82 as well as for current master. 2.18.2 is ok.
>>>
>>>
>>>
Thomas Morley writes:
> 2018-07-01 21:13 GMT+02:00 David Kastrup :
>
>> Perhaps try running under a debugger and setting a breakpoint on
>> ::warning (or so)? Then make a traceback when the warning is reached
>> (hopefully from the right point).
>
> Well, I don't know what I should do. I never
2018-07-01 23:07 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2018-07-01 21:13 GMT+02:00 David Kastrup :
>>
>>> Perhaps try running under a debugger and setting a breakpoint on
>>> ::warning (or so)? Then make a traceback when the warning is reached
>>> (hopefully from the right
10 matches
Mail list logo