lilypond-devel
[Top][All Lists]
Advanced

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

Re: Patch for LaTeX lilypond-syntax change


From: Carl Sorensen
Subject: Re: Patch for LaTeX lilypond-syntax change
Date: Mon, 19 Apr 2010 12:42:17 -0600



On 4/19/10 11:49 AM, "David Kastrup" <address@hidden> wrote:

> Graham Percival <address@hidden> writes:
> 
>> On Mon, Apr 19, 2010 at 10:54:15AM +0200, David Kastrup wrote:
>>> David Kastrup <address@hidden> writes:
>>> 
>>>> 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 like the general idea; I'll try testing it tomorrow.
>> 
>> A few caveats:
>> - we definitely need a CHANGES entry for this syntax change.
> 
> I don't know how to do this one.

Simply put an entry in Documentation/changes.tely that describes the new
lilypond-book syntax.  There's a guide to those changes in the top of
Documentation/changes.tely.

<snip>

> Done.  Somewhat annoyingly, one occurence is
> 
> Documentation/misc/CHANGES-0.1:969:     - changed \begin[options]{mudela} to
> \begin{mudela}[options]
> 
> This suggests that in version 0.1 somebody already fixed exactly that
> LaTeX syntax problem 12 years ago.  And the fix did not survive.

Maybe that's why there was that piece of code that didn't make any sense....


HTH,

Carl





reply via email to

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