[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Syntax for make-dynamic-script
From: |
Colin Hall |
Subject: |
Re: Syntax for make-dynamic-script |
Date: |
Mon, 21 Jan 2013 13:19:54 +0000 |
User-agent: |
mu4e 0.9.9.5-dev6; emacs 23.3.1 |
David Kastrup writes:
> Colin Hall <address@hidden> writes:
>
>> David Kastrup writes:
>>
>>> Colin Hall <address@hidden> writes:
>>>
>>>> David Kastrup <dak <at> gnu.org> writes:
>>>>
>>>>>
>>>>> Richard Shann <richard.shann <at> virgin.net> writes:
>>>>>
>>>>> > On Sat, 2012-12-22 at 00:58 +0100, David Kastrup wrote:
>>>>> > I guess this $ notation is documented somewhere - searching around
>>>>> > yesterday evening I came across this
>>>>> > http://lilypond.org/doc/v2.16/Documentation/notation/expressive-marks-
>>>> attached-to-notes#index-DynamicText
>>>>> >
>>>>> > which is where I suspect I got the notation I was using. Should that be
>>>>> > using $ too
>>>>>
>>>>> I repeat: with the exact given examples in the manual, the location data
>>>>> is correct.
>>>>
>>>> Thanks for your help with this, David, it looks like
>>>> Richard is able to engrave his music.
>>>>
>>>> Could you give me some advice on forming a good
>>>> documentation enhancement tracker for
>>>> the "$(" syntax? Perhaps there's a description
>>>> in a commit that I can use.
>>>
>>> Well, I have been thinking a bit about it. When using music via #...,
>>> the music really needs to be constructed for single use and not used
>>> somewhere else.
>>
>> It would be great to sort that out, but there is a more fundamental
>> problem that I'd like to address.
>>
>> The presence of the $(..$) syntax is undocumented and I would like to
>> create a tracker to capture that fact.
>
> <URL:http://lilypond.org/doc/v2.16/Documentation/extending/lilypond-scheme-syntax>
>
> <URL:http://lilypond.org/doc/v2.16/Documentation/extending/importing-scheme-in-lilypond>
>
> And it's not like those are not listed in the index:
>
> <URL:http://lilypond.org/doc/v2.16/Documentation/extending/lilypond-index>
Thanks, David, that's fine then.
Cheers,
Colin.
--
Colin Hall