Simon Albrecht writes:
> On 18.07.2018 10:59, David Kastrup wrote:
>> basically one of the calls to \offset gets junked because of LilyPond
>> not being able to disentangle them (one could extend the code to handle
>> this case but it would still balk at more complex combinations).
>
> Great! Thi
On 18.07.2018 10:59, David Kastrup wrote:
basically one of the calls to \offset gets junked because of LilyPond
not being able to disentangle them (one could extend the code to handle
this case but it would still balk at more complex combinations).
Great! This is exactly what would be needed in
Simon Albrecht writes:
> Hello everybody,
>
> this combination of a custom music function that combines the music
> simultaneously with itself and a \once\offset command causes LilyPond
> to crash (exit with return code 11):
>
>
> \version "2.19.82"
> test =
> #(define-music-function
On 17.07.2018 20:46, David Kastrup wrote:
I got
Tracker issue: 5386 (https://sourceforge.net/p/testlilyissues/issues/5386/)
Rietveld issue: 367760043 (https://codereview.appspot.com/367760043)
Issue description:
Make grob-transform robust against cloned invocations Well,
"robust" is a bit
Aaron Hill writes:
> On 2018-07-17 11:46, David Kastrup wrote:
>> Aaron Hill writes:
>>> I tried manually duplicating the music:
>>>
>>>
>>> \version "2.19.82"
>>> music = { \once \offset length 5 Stem c'4 c'4 }
>>> musicCopy = { \once \offset length 5 Stem c'4 c'4 }
>>> \new Staff
On 2018-07-17 11:46, David Kastrup wrote:
Aaron Hill writes:
I tried manually duplicating the music:
\version "2.19.82"
music = { \once \offset length 5 Stem c'4 c'4 }
musicCopy = { \once \offset length 5 Stem c'4 c'4 }
\new Staff { c'4 << \music \musicCopy >> c'4 }
This var
Aaron Hill writes:
> On 2018-07-15 20:09, Aaron Hill wrote:
>> Seems the custom music function is not needed to reproduce a crash.
>>
>>
>> \version "2.19.82"
>> music = { \once \offset length 5 Stem 4 4 }
>> << \music \music >>
>>
>>
>> This also results in:
>>
>>> GNU LilyPond 2
David Kastrup writes:
>> David mentioned two issues: using `<<...>>` top-level and using
>> unpitched notes.
>>
>> Consider the following not-quite-as-minimal example:
>>
>>
>> \version "2.19.82"
>> music = { \once \offset length 5 Stem c'4 c'4 }
>> \new Staff { c'4 << \music \music >>
Aaron Hill writes:
> On 2018-07-15 20:09, Aaron Hill wrote:
>> Seems the custom music function is not needed to reproduce a crash.
>>
>>
>> \version "2.19.82"
>> music = { \once \offset length 5 Stem 4 4 }
>> << \music \music >>
>>
>>
>> This also results in:
>>
>>> GNU LilyPond 2
On 2018-07-15 20:09, Aaron Hill wrote:
Seems the custom music function is not needed to reproduce a crash.
\version "2.19.82"
music = { \once \offset length 5 Stem 4 4 }
<< \music \music >>
This also results in:
GNU LilyPond 2.19.82
Processing `crash.ly'
Parsing...
Interpretin
On 2018-07-15 18:21, Simon Albrecht wrote:
Hello everybody,
this combination of a custom music function that combines the music
simultaneously with itself and a \once\offset command causes LilyPond
to crash (exit with return code 11):
\version "2.19.82"
test =
#(define-music-functi
Hello everybody,
this combination of a custom music function that combines the music
simultaneously with itself and a \once\offset command causes LilyPond to
crash (exit with return code 11):
\version "2.19.82"
test =
#(define-music-function (parser location mus) (ly:music?)
#{
12 matches
Mail list logo
