"m...@apollinemike.com" writes:
> Le Dec 6, 2011 à 2:01 PM, David Kastrup a écrit :
>
>> "m...@apollinemike.com" writes:
>>
>>> Hey all,
>>>
>>> I believe that the variable `clone' needs to be unquoted in commit
>
David Kastrup writes:
> "m...@apollinemike.com" writes:
>>
>> If one defines a music function incorrectly and then tries to use it, i.e. :
>>
>> foo =
>> #(define-music-function (parser location)
>> #{ a #})
>>
>> \foo
>>
>> One gets the following warning message:
>>
>> Parsing...
>> foo.ly:4:1:
"m...@apollinemike.com" writes:
> Le Dec 6, 2011 à 2:01 PM, David Kastrup a écrit :
>
>> "m...@apollinemike.com" writes:
>>
>>> Hey all,
>>>
>>> I believe that the variable `clone' needs to be unquoted in commit
>
Le Dec 6, 2011 à 2:01 PM, David Kastrup a écrit :
> "m...@apollinemike.com" writes:
>
>> Hey all,
>>
>> I believe that the variable `clone' needs to be unquoted in commit
>> 4778c7326d726f50f6ac541322006d6b90795945 (it is part of a quasi-quoted
&
"m...@apollinemike.com" writes:
> Hey all,
>
> I believe that the variable `clone' needs to be unquoted in commit
> 4778c7326d726f50f6ac541322006d6b90795945 (it is part of a quasi-quoted
> list). I haven't tested it thoroughly, but please give it a look and
Hey all,
I believe that the variable `clone' needs to be unquoted in commit
4778c7326d726f50f6ac541322006d6b90795945 (it is part of a quasi-quoted list).
I haven't tested it thoroughly, but please give it a look and lemme know if
this is indeed the case.