Re: Paper size bleeds across lilypond runs

[Phil Holmes]

----- Original Message ----- 
From: "David Kastrup" <address@hidden>
To: <address@hidden>
Sent: Saturday, March 16, 2013 3:16 PM
Subject: Re: Paper size bleeds across lilypond runs


> David Kastrup <address@hidden> writes:
>
> > "Phil Holmes" <address@hidden> writes:
> >
> > > Invoking lilypond using the read-file-list option and job-count of 9,
> > > I get output image files of varying sizes.  This is messing up my
> > > pixel comparator regtest checker.  I've tracked it down to the use of
> > > #(set-default-paper-size "A6") in one of the regtests.  Once this has
> > > been used, it changes the default paper-size for all output created
> > > with that instance of lilypond.  I've read the NR and I know it's
> > > supposed to affect the whole of the scope it applies to, but not
> > > surely all the subsequent files in a multi-run job?
> > >
> > > Bug?
> >
> > Sounds like it.
>
> Though -dpaper-size should likely be for the whole kaboodle.
>
> --
> David Kastrup


It gets permanently over-written by the set-default-paper-size command. 
I've fixed my problem by putting a

\paper {
 #(set-paper-size "A4")
}

in my "init" file, but it's not ideal.

--
Phil Holmes