Patch for LaTeX lilypond-syntax change (was: Rationale for LaTeX lilypond-book syntax?)

[David Kastrup]

David Kastrup <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>
>> Carl Sorensen <address@hidden> writes:
>>
>>> Actually,  [c16 d e f] is *not* valid lilypond.  The first brace needs to
>>> come after the c16:
>>
>>> So I don't think there's a problem with the options coming after the
>>> {lilypond}.
>>
>> Oh right.  Wow.
>
> Took a look at lilypond-book.py.  Did one change and am just now
> recompiling.
>
> The change is fairly obvious (hope it works):

It didn't, but the following on Rietveld should:

<URL:http://codereview.appspot.com/813048>

I still have no clue about the following, though:

> However, I am doing this more or less pattern-based without any
> knowledge of the program structure, and lilypond-book.py _also_ contains
>
>         FILTER: r'''\begin{lilypond}[%(options)s]
> %(code)s
> \end{lilypond}''',
>
> which already _has_ the normal LaTeX order for some reason.  So what
> gives?

-- 
David Kastrup