bug-lilypond
[Top][All Lists]
Advanced

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

Re: scheme function doesn't work anymore


From: VSD
Subject: Re: scheme function doesn't work anymore
Date: Tue, 14 Jun 2005 19:21:21 +0200
User-agent: Opera M2/8.0 (Win32, build 7561)

Thanks for the answer. Indeed \mychords are within a \score block. The exact input file is:

%%%%%%%%%%

ChordOffset = #(def-music-function (parser location offset) (pair?)
    #{
        \override ChordNames.ChordName #'extra-offset = #$offset
    #}
)

mychords = \chordmode
{
    \ChordOffset #'(-0.75 . 0)
     ges2:maj7.4+ des2:9
}

\score { \mychords }

%EOF%

That's strange if this works for you. I've done a fresh install of 2.5.29-2 (instead of an upgrade) and still have the problem. I'm using now LilyTool for jEdit, and the internal console shows another clue when trying to compile:

Processing `C:/music/kk.ly'
Parsing...ERROR: Unbound variable: lilyvartmpc

Shuch error don't appears in the log file. It just stucks on "Parsing...".

Nevertheless, moving back to version 2.5.29-1 compiles the file perfectly.

┬┐What I'm missing?

Vincent (Confused)



On Tue, 14 Jun 2005 17:30:41 +0200, Mats Bengtsson <address@hidden> wrote:

I hope you include \mychords within a \score{...} block,
otherwise you won't get any output. I tried your lines of code
extended with
\score{\mychords}
and certainly get some output using 2.5.30.

    /Mats

VSD wrote:
I was successfully using the following simple scheme function in all the 2.5.x series until 2.5.29-1 (all win native under WXP):
 ChordOffset = #(def-music-function (parser location offset) (pair?)
    #{
        \override ChordNames.ChordName #'extra-offset = #$offset
    #}
)
 mychords = \chordmode
{
    \ChordOffset #'(-0.75 . 0)
     ges2:maj7.4+ des2:9 ...
}
 but in version 2.5.29-2 this doesn't work anymore. The log file is:
 # -*-compilation-*-
Changing working directory to `C:/music/tst'
Processing `C:/music/kk.ly'
Parsing...
... and I don't get any output file. If I replace the function call by the corresponding lilypond code:
 \override ChordNames.ChordName #'extra-offset = #'(-0.75 . 0)
 then it works as expected.
 Is this a bug or am I doing something wrong?
 Thanks and greetings,
 Vincent
    _______________________________________________




reply via email to

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