[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 334 in lilypond: setting staff size not longer safe
From: |
codesite-noreply |
Subject: |
Issue 334 in lilypond: setting staff size not longer safe |
Date: |
Tue, 11 Sep 2007 17:25:02 -0700 |
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #2 by gpermus:
Really?! To clarify, I'm talking about lilypond raising an error with
-dsafe
It's a nitpick (err, sorry, should have been Priority-Low), but in a previous
version
it _was_ accepted as a "safe" command.
With the 2.11.32 linux-x86, I get this:
address@hidden:~/tmp$ lilypond -dsafe foo.ly
GNU LilyPond 2.11.32
Processing `foo.ly'
Parsing...
foo.ly:2:1: error: GUILE signaled an error for the expression beginning here
#
(set-global-staff-size 16)
Unbound variable: $defaultpaper
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `foo.ps'...
Converting to `foo.pdf'...
error: failed files: "foo.ly"
Issue attribute updates:
Labels: -Priority-Medium Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings