bug-lilypond
[Top][All Lists]
Advanced

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

overrides and GUILE errors


From: Justin Gregory
Subject: overrides and GUILE errors
Date: Tue, 16 Dec 2008 23:04:39 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

> I'm not top posting.

It seems that whenever I try to use an \override command, I get strange GUILE
errors, and then the lilypond type-check fails.  However, if I add a comment to
the end of the line (it doesn't matter what the comment says), there is no
error.  I'm using Ubuntu 8.04 on an i386, lilypond 2.10.33, and Guile says it is
version 1.8.3.  Here is an input file that produces the error on my system:

\version "2.10.33"

dummyWords = \lyricmode

{

        % Adding a comment after the end of the next line causes the error to 
go away...
        \override Score . LyricText #'font-size = #-1

        \override LyricHyphen #'minimum-distance = #1 %These don't work without 
a
comment???

        Let us with a glad -- some mind

}


\score

{
        <<

                \new Staff
                <<

                        \new Voice = "sopranos"

                        {

                                \relative f'

                                {

                                        a4. g8 f4 d' | c bes a2 
                                }
                        }


                        \new Lyrics = dummy { s1 }

                >>
                \context Lyrics = dummy \lyricsto sopranos \dummyWords

        >>

}


And this is the output of running lilypond:

GNU LilyPond 2.10.33
Processing `error.ly'
Parsing...
error.ly:6:45: error: GUILE signaled an error for the expression beginning here
  \override Score . LyricText #'font-size = #
                                             -1
}#bound variable: #{-1\
Interpreting music... 
warning: type check for `font-size' failed; value `#<unspecified>' must be of
type `number'
[2]
Preprocessing graphical objects...
Layout output to `error.ps'...
Converting to `error.pdf'...
error: failed files: "error.ly"

It's easy enough to get around the error by adding comments, but this seems to
be a bug to me, and I nearly pulled out all of my hair before I accidentally
discovered the comment trick.





reply via email to

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