Matthew gmail.com> writes:
>
> Is there a way to have /include keep relative path information?
>
I've got a work around that only works because of my simple, one level directory
structure
def/master_def.ly
\version "2.11.43"
\include "../def/note_def.ly"
%some other stuff
.
s
On 12 Apr 2008, at 18:17, Valentin Villenave wrote:
Is there a way to have /include keep relative path information?
Currently there isn't (and I find it very much annoying, which is why
I proposed to sponsorize this implementation).
See
http://code.google.com/p/lilypond/issues/detail?id=391
I
2008/4/12 Matthew <[EMAIL PROTECTED]>:
> Is there a way to have /include keep relative path information?
Currently there isn't (and I find it very much annoying, which is why
I proposed to sponsorize this implementation).
See
http://code.google.com/p/lilypond/issues/detail?id=391
Cheers,
Valent
Hi Matthew,
If the file isn't in the local directory, or lily search path,
you have to specify additional path with -I [capital i], such as:
lilypond -I
I have made a simple script to myself which does this for me:
#!/bin/bash
lilypond -I/usr/alto/projects/music/scores/
Hi all
I'm setting up a bunch of different settings for my scores. I've put them into a
separate definition file so that I can just \include it.
I have several different definition files feeding into a master definition file,
and I include the master file in my score. My definition files are stor
