Re: command line parameters to set the papersize

[Juergen Reuter]

Hi,

what about specifying paper size, layout, global staff size, etc. in a 
separate file, say defs.ly, and \include it at the very beginning of the 
actual score file?  This file would then serve as a kind of (very 
primitive) style sheet.  You still could override e.g. global staff size 
immediately after the \input in the score file.

What I could imagine to be useful is a command line option for including 
an additional file (like the above defs.ly) at the very beginning of the 
score file.  Still, even that should be already possible by (abusing) the 
-i option: just say "-i defs.ly" and put '\input "init.ly"' at the very 
beginning of the defs.ly file (untested).

Greetings,
Jürgen

On Thu, 13 Jan 2005, Ruud van Silfhout wrote:

> Hi,
> 
> As you probably know by now, I recently joined the Mutopia team to help with
> the maintenance of te music and the development of the site.
> One of the things we want to do is make an svn-repository and have an
> automatic build process that generates all music documents from that tree.
> To be able to do that the idea is that we need some kind of commandline
> parameter to select the paper-size as all music pieces are available on
> Mutopia in both A4 and letter size.
> Chris, one of the other mutopia maintainers, posted recently a request
> regarding this issue on
> the lilypond user list, but he did not get any reply. So, I re-post it on
> the devel list.
> Anyone willing to help us out ?
> 
> Bye
> Ruud van Silfhout
> Mutopia maintainer
> mailto://Ruud.vanSilfhout(at)MutopiaProject.org
> 
> > Hi,
> >
> > I've been trying to figure out if it's possible to set the paper size of
> > Lilypond's output from the command line in version 2.4. In version 2.2, I
> > used to use --set=papersize="letter", however this option seems to have
> > been removed.
> 
> > I thought that -e "(set-default-paper-size \"letter\")" might work, but I
> get
> > the following error message. I'm not sure if I'm trying the right approach
> > here, or maybe this is a bug. Are any gurus able to help?
> 
> > Thanks in advance,
> >
> > Chris
> 
> Regards,
> Ruud van Silfhout
> 
> 
> 
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
>