[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Syntax for make-dynamic-script
From: |
David Kastrup |
Subject: |
Re: Syntax for make-dynamic-script |
Date: |
Mon, 21 Jan 2013 11:19:11 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
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.
Huh.
<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>
> I have looked for a mention of it in the source for the parser, the
> issue tracker and the commit history, all to no avail.
Huh. We _do_ have actual documentation, not just information that can
be tracked by experienced programmers.
But then it seemed easy enough to find
<URL:http://code.google.com/p/lilypond/issues/detail?id=2024> which
streamlined $ behavior inside and outside of #{ ... #} (it was
previously only available inside, and with strange semantics).
And that includes documentation.
> Can you please supply some information for this feature, which I
> believe you introduced, so that it can be documented.
Perhaps you should explain what is wrong with the existing
documentation.
--
David Kastrup