[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Patch for LaTeX lilypond-syntax change (was: Rationale for LaTeX lilypon

From: David Kastrup
Subject: Patch for LaTeX lilypond-syntax change (was: Rationale for LaTeX lilypond-book syntax?)
Date: Mon, 19 Apr 2010 10:54:15 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.92 (gnu/linux)

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  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:


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 _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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]