Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
Aaron Hill writes: > convert-ly knows how to fix this: > > > \override Thing #'property #'sub-property = #'value > % ...to... > \override Thing.property.sub-property = #'value > > > It does not however seem to correct: > > > variable #'key = #'value > % ...to... > variable.key = #'value > commit 10df1245877fb5e16410388ef42b71c9aa06a9d9 Author: David Kastrup Date: Mon Mar 30 00:49:14 2020 +0200 Issue 5872: convert-ly rule for 2.19.39 as cleanup for issue 4800 That issue made previously valid and promoted code invalid without proper replacement. Property assignments of the form staffgroup-staff-spacing #'basic-distance = #15 are converted to staffgroup-staff-spacing.basic-distance = #15 for various paper or layout spacing variables. The problem is that this convert-ly rule was done rather late and so you need at least convert-ly from 2.21.0 to get this right. So if you used an older convert-ly for getting your version across 2.19.39, this convert-ly fix will no longer get applied. The good news should be that the given score should work in 2.21.x+ again assuming that you convert it all the way from its ancient version with the new convert-ly. Of course it would also work in 2.20 if you use the latest convert-ly to go just up to 2.20. But who does that? -- David Kastrup
Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
That works!
Thanks,
Ken
On Sun, Nov 29, 2020 at 1:08 PM Aaron Hill wrote:
>
> On 2020-11-29 12:03 pm, Kenneth Wolcott wrote:
> > Hi;
> >
> > I downloaded a Mutopia Greensleves ly source and successfully
> > converted it to 2.20.0 but get the following error when engraving:
> >
> > ././updated_greensleeves.ly:68:22: error: syntax error, unexpected
> > SCM_TOKEN, expecting ',' or '.' or '='
> > top-markup-spacing
> > #'padding = #10
> >
> > The output from convert was only the version numbers.
> >
> > Please tell me how to fix this.
> >
> > The engraving did succeed as there were pdf and midi files produced.
> >
> > The paper section, below, is where the error occurs:
> >
> > \paper {
> > first-page-number = 2
> > print-first-page-number = ##t
> > top-markup-spacing #'padding = #10
> > markup-system-spacing #'padding = #7
> > system-system-spacing #'basic-distance = #14
> > }
>
> convert-ly knows how to fix this:
>
>
>\override Thing #'property #'sub-property = #'value
> % ...to...
>\override Thing.property.sub-property = #'value
>
>
> It does not however seem to correct:
>
>
>variable #'key = #'value
> % ...to...
>variable.key = #'value
>
>
>
> -- Aaron Hill
>
Re: Syntax error encountered while engraving a successfully updated Mutopia ly file
On 2020-11-29 12:03 pm, Kenneth Wolcott wrote:
Hi;
I downloaded a Mutopia Greensleves ly source and successfully
converted it to 2.20.0 but get the following error when engraving:
././updated_greensleeves.ly:68:22: error: syntax error, unexpected
SCM_TOKEN, expecting ',' or '.' or '='
top-markup-spacing
#'padding = #10
The output from convert was only the version numbers.
Please tell me how to fix this.
The engraving did succeed as there were pdf and midi files produced.
The paper section, below, is where the error occurs:
\paper {
first-page-number = 2
print-first-page-number = ##t
top-markup-spacing #'padding = #10
markup-system-spacing #'padding = #7
system-system-spacing #'basic-distance = #14
}
convert-ly knows how to fix this:
\override Thing #'property #'sub-property = #'value
% ...to...
\override Thing.property.sub-property = #'value
It does not however seem to correct:
variable #'key = #'value
% ...to...
variable.key = #'value
-- Aaron Hill
Re: Syntax error, unexpected UNSIGNED
I just fund out that it only works with version 2.19. Sorry for the spam, I
was getting crazy.
El mar., 15 de may. de 2018 a la(s) 19:01, Andrés Westra <
westra...@gmail.com> escribió:
> Hi, I,m working in a project an suddenly this error apears. I no longer
> can write:
>
> \version "2.18.2"
> \relative {c4 8 8 8. 16}
>
> This apears in the logs:
>
> error: syntax error, unexpected UNSIGNED
>
> \relative {c4
>
>8 8 8. 16}
>
>
>
> Before I was able to write that, now it only works if I write this:
>
>
> \version "2.18.2"
> \relative {c4 c8 c c8. c16}
>
> Thanks for the help.
>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On 11/08/2013 12:37 PM, taylor...@sky.com wrote: Hi, I seem to keep getting a syntax error, and I don't know why can someone help please?? The error I keep getting is: # -*-compilation-*- Processing `C:/Users/staff/Desktop/first try.ly' Parsing... C:/Users/staff/Desktop/first try.ly:37:1: error: syntax error, unexpected } fatal error: failed files: C:\\Users\\staff\\Desktop\\first try.ly Can someone please help? First, the error message shows you where it began to go wrong. Unexpected . . . anything, in LilyPond terms, usually means you haven't paired your curly braces properly, and yes, that is most of your problem. Another thing which will give you problems is that ties only join notes of equal pitch; you need slurs to connect d to c. More generally, when faced with this sort of issue, your first steps would be to start eliminating things until the problem goes away, then take a hard look at the last thing you cut. Having trimmed the code to the bare minimum which produces the problem, you are much more likely to get specific help from the community. I'm writing this because my wife wants me to come downstairs and move a couple of filing cabinets for her, in the face of my not inconsiderable reluctance. Finally, the canned response is a very firm suggestion that you work through the Learning Manual on the LilyPond website, having installed a syntax-highlighting editor beforehand. My favourite is undoubtedly Frescobaldi, but others are available. Cheers, Colin -- Excellent day for putting Slinkies on an escalator. - Dan Galvin, TFTD List 20070228 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
Hi Seb,
On Fri, Nov 8, 2013 at 1:37 PM, taylor...@sky.com taylor...@sky.com wrote:
Hi,
I seem to keep getting a syntax error, and I don't know why can someone
help please??
My code is:
\new Voice = soprano {
\relative c''{
\key f \major
\autoBeamOff
\time 4/4
\partial 4
a16 c d8 |
r4 ees8( d~ d4~ c d c |
d4. c8~ c) r a16 c d8 |
r4 ees8( d~ d4~ d16 c d c |
d8. ees16 d8 c~ c) r a16 c d8 |
r4 ees8( d~ d4~ d16 c d c |
d4. c8~ c) r a16 g f8 |
f1 |
r4 c' d f |
f2( e |
\times 2/3{ d4 e f~) f2) |
You don't close the \times expression (or the one below) with }.
f2( e |
\times 2/3{ d4 e f~) f2) |
}
}
HTH,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On Fri, Nov 8, 2013 at 8:11 PM, Colin Campbell c...@shaw.ca wrote: Finally, the canned response is a very firm suggestion that you work through the Learning Manual on the LilyPond website, having installed a syntax-highlighting editor beforehand. My favourite is undoubtedly Frescobaldi, but others are available. Yup--I automatically indented your code with Frescobaldi and the problem was immediately apparent. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On 11/08/2013 07:12 PM, David Nalesnik wrote:
Hi Seb,
On Fri, Nov 8, 2013 at 1:37 PM, taylor...@sky.com
mailto:taylor...@sky.com taylor...@sky.com
mailto:taylor...@sky.com wrote:
Hi,
I seem to keep getting a syntax error, and I don't know why can
someone help please??
My code is:
\new Voice = soprano {
\relative c''{
\key f \major
\autoBeamOff
\time 4/4
\partial 4
a16 c d8 |
r4 ees8( d~ d4~ c d c |
d4. c8~ c) r a16 c d8 |
r4 ees8( d~ d4~ d16 c d c |
d8. ees16 d8 c~ c) r a16 c d8 |
r4 ees8( d~ d4~ d16 c d c |
d4. c8~ c) r a16 g f8 |
f1 |
r4 c' d f |
f2( e |
\times 2/3{ d4 e f~) f2) |
You don't close the \times expression (or the one below) with }.
f2( e |
\times 2/3{ d4 e f~) f2) |
}
}
Actually, he probably closed both triplet phrases with ) instead of }
Cheers,
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On Mon, Oct 4, 2010 at 10:18 AM, alex stone compos...@gmail.com wrote:
I can't for the life of me figure out what i've done here. (new lily user)
Working in lilypondtool 2.12.894 (jedit 4.3.2), with lily 2.13.36
Here's the error:
%lilypond %args /home/alex/audio-projects/wobbly
Processing `/home/alex/audio-projects/wobbly'
Parsing...
/home/alex/audio-projects/wobbly:138:37: error: syntax error, unexpected
STRING
\set Staff.instrumentName =
Horn F 1
error: failed files: /home/alex/audio-projects/wobbly
Processing time: 1 seconds
Normally this error message is because of a missing curly brace
somewhere. From the code you included it's impossible to tell where
that might be--there's not enough code there. Check for missing {}.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
Hmmm, can't spot anything missing at the moment.
Here's the entire test file.
http://pastebin.com/pSu6Asge
Thanks for the reply,
Alex.
On Mon, Oct 4, 2010 at 7:34 PM, Jonathan Kulp jonlancek...@gmail.com wrote:
On Mon, Oct 4, 2010 at 10:18 AM, alex stone compos...@gmail.com wrote:
I can't for the life of me figure out what i've done here. (new lily user)
Working in lilypondtool 2.12.894 (jedit 4.3.2), with lily 2.13.36
Here's the error:
%lilypond %args /home/alex/audio-projects/wobbly
Processing `/home/alex/audio-projects/wobbly'
Parsing...
/home/alex/audio-projects/wobbly:138:37: error: syntax error, unexpected
STRING
\set Staff.instrumentName =
Horn F 1
error: failed files: /home/alex/audio-projects/wobbly
Processing time: 1 seconds
Normally this error message is because of a missing curly brace
somewhere. From the code you included it's impossible to tell where
that might be--there's not enough code there. Check for missing {}.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
--
www.openoctave.org
midi-subscr...@openoctave.org
development-subscr...@openoctave.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
Alex,
Your bassoon entry above the french horn is missing a closing for
the bar statement
\bar |.
On Mon, Oct 4, 2010 at 11:46 AM, alex stone compos...@gmail.com wrote:
Hmmm, can't spot anything missing at the moment.
Here's the entire test file.
http://pastebin.com/pSu6Asge
Thanks for the reply,
Alex.
On Mon, Oct 4, 2010 at 7:34 PM, Jonathan Kulp jonlancek...@gmail.com wrote:
On Mon, Oct 4, 2010 at 10:18 AM, alex stone compos...@gmail.com wrote:
I can't for the life of me figure out what i've done here. (new lily user)
Working in lilypondtool 2.12.894 (jedit 4.3.2), with lily 2.13.36
Here's the error:
%lilypond %args /home/alex/audio-projects/wobbly
Processing `/home/alex/audio-projects/wobbly'
Parsing...
/home/alex/audio-projects/wobbly:138:37: error: syntax error, unexpected
STRING
\set Staff.instrumentName =
Horn F 1
error: failed files: /home/alex/audio-projects/wobbly
Processing time: 1 seconds
Normally this error message is because of a missing curly brace
somewhere. From the code you included it's impossible to tell where
that might be--there's not enough code there. Check for missing {}.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
--
www.openoctave.org
midi-subscr...@openoctave.org
development-subscr...@openoctave.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Brett W. McCoy -- http://www.electricminstrel.com
In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world.
-- Jelaleddin Rumi
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On Mon, Oct 4, 2010 at 8:08 PM, Brett McCoy idragos...@gmail.com wrote:
Alex,
Your bassoon entry above the french horn is missing a closing for
the bar statement
\bar |.
On Mon, Oct 4, 2010 at 11:46 AM, alex stone compos...@gmail.com wrote:
Hmmm, can't spot anything missing at the moment.
Here's the entire test file.
http://pastebin.com/pSu6Asge
Thanks for the reply,
Alex.
On Mon, Oct 4, 2010 at 7:34 PM, Jonathan Kulp jonlancek...@gmail.com wrote:
On Mon, Oct 4, 2010 at 10:18 AM, alex stone compos...@gmail.com wrote:
I can't for the life of me figure out what i've done here. (new lily user)
Working in lilypondtool 2.12.894 (jedit 4.3.2), with lily 2.13.36
Here's the error:
%lilypond %args /home/alex/audio-projects/wobbly
Processing `/home/alex/audio-projects/wobbly'
Parsing...
/home/alex/audio-projects/wobbly:138:37: error: syntax error, unexpected
STRING
\set Staff.instrumentName =
Horn F 1
error: failed files: /home/alex/audio-projects/wobbly
Processing time: 1 seconds
Normally this error message is because of a missing curly brace
somewhere. From the code you included it's impossible to tell where
that might be--there's not enough code there. Check for missing {}.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
--
www.openoctave.org
midi-subscr...@openoctave.org
development-subscr...@openoctave.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Brett W. McCoy -- http://www.electricminstrel.com
In the rhythm of music a secret is hidden; If I were to divulge it,
it would overturn the world.
-- Jelaleddin Rumi
Brett, thanks, that did the trick.
Alex.
--
www.openoctave.org
midi-subscr...@openoctave.org
development-subscr...@openoctave.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
Hmmm, can't spot anything missing at the moment. Here's the entire test file. http://pastebin.com/pSu6Asge Hi Alex! Another noob here... Take a look at line 133. Looks like you're missing a closing quote. Regards, Jeff ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
- Original Message - From: alex stone compos...@gmail.com Hmmm, can't spot anything missing at the moment. Here's the entire test file. http://pastebin.com/pSu6Asge Thanks for the reply, Alex. Alex, Please look at the Learning Manual for 2.12.3 - section 5.2 - When things don't work. This explains exactly how you could have found this error yourself, and learnt a little about the syntax at the same time. Hope this helps. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error
On Mon, Oct 4, 2010 at 8:25 PM, Phil Holmes m...@philholmes.net wrote: - Original Message - From: alex stone compos...@gmail.com Hmmm, can't spot anything missing at the moment. Here's the entire test file. http://pastebin.com/pSu6Asge Thanks for the reply, Alex. Alex, Please look at the Learning Manual for 2.12.3 - section 5.2 - When things don't work. This explains exactly how you could have found this error yourself, and learnt a little about the syntax at the same time. Hope this helps. -- Phil Holmes Ok, thanks for the heads up. Alex. -- www.openoctave.org midi-subscr...@openoctave.org development-subscr...@openoctave.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax error using \midi directive
This compiles fine with Lilypond 2.13.0. Are you sure you sent the
actual content of you .ly file? Without the original file it may be
mystic to us.
Regards,
Helge
Jörg Krause schrieb:
Hi to all,
I am getting a (almost to me) mysterial syntax error
lodi_vespri/musiche/psalmen_joerg.ly:65:17: Fehler: syntax error,
unexpected '}', expecting '='
\midi {
compiling the following source (the line which produces the error is
marked):
Thanks for your help.
mailto:jrgkr...@googlemail.com
\version 2.13.3
VierzeiligErsterOben = \relative c''
{ \key f \major
{ c,4 a8 c d2 | f4 g8 a f2 | a4 g8 f g2 | f4 e8 d e4 d4 | } \\
{ s1 | d2 c2 | c1 | d4 s4 s2| }
}
VierzeiligErsterUnten = \relative c'
{ \key f \major
{ e2 f a2 | f~ bes2 f~ a~ | f a e g | g bes2. a
f4 | }
}
DreizeiligErsterOben = \relative c''
{ \key f \major
{ a g8 f g2 g4~ g8 a f2 f4 d8 f g4 f4 } \\
{ c1d s2 c2}
}
DreizeiligErsterUnten = \relative c
{ \key f \major \clef bass
f4 a e2 bes'2 a2 { bes2~ bes4 a4 } \\ { f~ d2 f }
}
ZweizeiligErsterOben = \relative c''
{ \key f \major
{ a4 g8 a d,2 g4 f8 g a2 } \\
{ c,2 s d e } \bar ||
}
ZweizeiligErsterUnten = \relative c
{ \key f \major \clef bass % Untere Zeile
{ s4 a bes a bes c cis2 } \\
{ f,1 g2a4 g }
\bar || }
ZweizeiligZweiterOben = \relative c'
{ \key c \major
{ c2^Version 2 g' a g } \\
{ s2 d c d }
}
ZweizeiligZweiterUnten = \relative c
{ \key c \major
{ e4 f c' b s2b2} \\
{ g1 f4 g8 a g4 f }
}
\header {
title = Begleitmusik für Psalmen
subtitle = Gesetzt von Jörg Krause
}
\score {
\new PianoStaff {
\new Staff \VierzeiligErsterOben
\new Staff \VierzeiligErsterUnten
}
\header {
piece = 4 Zeilen
}
\layout { }
\midi { } %## Line where the error is #
}
\score {
\new PianoStaff
\new Staff \DreizeiligErsterOben
\new Staff \DreizeiligErsterUnten
\header {
piece = 3 Zeilen
}
}
\score {
\new PianoStaff
\new Staff { \ZweizeiligErsterOben \ZweizeiligZweiterOben }
\new Staff { \ZweizeiligErsterUnten \ZweizeiligZweiterUnten }
\header {
piece = 2 Zeilen
}
\layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error SCM_TOKEN?
Hi Everybody, I found the problem. The init.ly file helped me. There was a strange ascii shape at the end of my file. Weird. Craig Bakalian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error SCM_TOKEN?
Craig Bakalian wrote: Hi Everybody, I found the problem. The init.ly file helped me. There was a strange ascii shape at the end of my file. Weird. Craig Bakalian These kind of errors annoy me to death since I'm using a Mac. Lily, LaTeX, several compilers; everything complains about the typographic whitespace characters which are simple to type in on a Mac. Haven't figured out all the keystrokes, but as far as I know, you can type non-breaking spaces, en and em-spaces, and may be others (line breaks?) with great ease. Of course, all of them are specified in UTF and, thus, wrote as such into plain text files, and you can't distinguish them in most editors, especially using a monospace font. I don't see hope for LaTeX fixing this in the short term; but since at least Lilypond is made to deal with Unicode, it would be nice if those characters could be handled by the parser as what they are - whitespaces. For the meantime - anybody knows how to convince Smultron to mark those characters? Or, even better - is there a program which temporarily shuts off typographic character shortcuts for the whole system? Alexander ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error SCM_TOKEN?
Am 2008-05-03 um 20:15 schrieb Alexander Kobel: For the meantime - anybody knows how to convince Smultron to mark those characters? Or, even better - is there a program which temporarily shuts off typographic character shortcuts for the whole system? TextWrangler at least can show such invisible characters - and is great in converting encodings. (And it's one of the few editors that are not too slow on my old G4.) Greetlings from Lake Constance --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error SCM_TOKEN?
These kind of errors annoy me to death since I'm using a Mac. Lily,
LaTeX, several compilers; everything complains about the typographic
whitespace characters which are simple to type in on a Mac.
What's the problem with LaTeX? You simply say
\usepackage[utf8]{inputenc}
and most of those typographic spaces are automatically mapped to the
right LaTeX entities. Otherwise, simply use \DeclareUnicodeCharacter
and define something for it.
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error
Gordon Gilbert gord at angel.eicat.ca writes:
Then I changed something else (and I can't seem to restore it with undo
in xemacs) and it now gives me:
Gloria4Part.ly:20:10: error: syntax error, unexpected DIGIT
\version
2.5.29
error: failed files: Gloria4Part.ly
\header {
lastupdated = 2005/September/5
}
\version 2.5.29
Hello!
I haven't used the lastupdated property myself, but I believe the date would
need to be enclosed within quotes. However, it looks like you're missing one at
the end of the date.
Since this is immediately above your version statement, I suppose that's what's
causing the problem
Hope this helps :)
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Syntax Error in compiling
Gordon Gilbert gord at angel.eicat.ca writes:
Hi again!
Thanks to Andrew for showing me where the error was -- and SO SIMPLE!!
Can someone please explain how to read the error messages when lilypond
fails to compile a file? For example, the bit the program quoted was
*after* the error -- is this standard?
Blessings,
Fr. Gordon Gilbert+
+=+
| Angels' Roost Farm |
| Rev. Fr. Gordon Gilbert Susan Gilbert |
| 705-549-5056 |
|gord at angel.eicat.ca |
|susan at angel.eicat.ca|
+=+
Usually, if you can't find anything blatantly wrong in the program output, you
would suppose the error is somewhere further up. Sometimes it can be a *lot*
further, depending on what you're doing.
In this particular case, whatever is between two quotes is considered a string
(text). Since the closing quote is missing, the compiler is simply going to
continue through the file until it finds a matching quote (which obviously isn't
the right one). So what happens here, is that the closing brace is considered as
text by the compiler, and not a part of the program structure.
\header {
lastupdated = 2005/September/5
}
\version 2.5.29
as far as the compiler is concerned, lastupdated is something like:
2005/September/5 } \version
it thinks that it's still in the \header section, since it hasn't found a
closing brace, and now stumbled upon a series of numbers ( 2.5.29 ) which
clearly shouldn't be there on its own. And that's why it points you to the
version number instead of the missing quote.
I hope this all makes sense,
All the best,
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: syntax error
Fr. Gordon Gilbert wrote:
I'm using 2.5.29 . . . I need letter instead of A4 . . .
Parsing...
warning: Must use #(set-paper-size .. ) within \paper { ... }
. . . my #(set-paper-size) was withing \layout . . .
So I moved that to the top of the file within a \paper block.
The first time I compiled that, it did just fine, but did
not change the paper size.
I use 2.6.0, and putting the following two lines at the very top of the
file works for me:
\version 2.6.0
#(set-default-paper-size letter)
Of course 2.5.29 might be different, but it might be worth trying to set
the default paper size at the top level just to see if it works.
-- Tom
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
