David Kastrup <d...@gnu.org> writes:
> David Kastrup <d...@gnu.org> writes:
>
>> Carl Sorensen <c_soren...@byu.edu> 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
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
