bug-lilypond
[Top][All Lists]
Advanced

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

Re: Error message


From: Mats Bengtsson
Subject: Re: Error message
Date: Fri, 05 Dec 2003 15:42:45 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

It seems that convert-ly does some errors in converting
\spanrequest \start "text"
Just edit your converted file and replace, for example,
#(ly:export (make-span-event 'TextSpanEvent START) g8)
with
\startTextSpan g8
and
#(ly:export (make-span-event 'TextSpanEvent STOP))
with
\stopTextSpan

   /Mats

Thomas Dent wrote:
Hi, I've just converted a large file from 1.5.x to 2.0 and it seems to be
failing at one point. The log file is as follows:

*****

lilypond (GNU LilyPond) 2.0.1
Running usr...
Now processing: `jonson.ly'
Parsing...ERROR: Unbound variable: fis2

lilypond: error: LilyPond failed on input file jonson (exit status 2)
lilypond: warning: Running LilyPond failed. Rerun with --verbose for a
trace.

*****

With --verbose, I get (among other things)

*****

Backtrace:
In (/filepath)/jonson.ly:
   1: 0* [ly:export #<Music TextSpanEvent> ...

(/filepath)/jonson.ly:1:66: While evaluating arguments to ly:export in
expression (ly:export (make-span-event # START) fis2):
(/filepath)/jonson.ly:1:66: Unbound variable:fis2
lilypond: warning: `usr' failed (status 2) (ignored)

*****

Any suggestions?

Thomas Dent


_______________________________________________
Lilypond-user mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/lilypond-user

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================





reply via email to

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