Here's a summary of information gleaned from this thread and some
experimentation. Thanks to all the contributors.
- Bruce
==========================================================
\include "<filename.ly>"
The initialization of LilyPond is done in a number of files that are
included when you start the program, normally transparent to the user. Run
lilypond --verbose to see a list of paths and files that Lily finds.
You may cause additional files to be included. The line \include "file.ly"
is equivalent to pasting the contents of file.ly into the current file at
the place where you have the \include.
Files placed in directory ...\usr\share\lilypond\2.4.6\ly (or current
version number) are on the path and available to \include. Files in the
current working directory are available to \include, but a file of the same
name in ...\usr\share\lilypond\2.4.6\ly takes precedence. Files are
available to include from directories in the search path specified as an
option when invoking "lilypond --include=DIR" which adds DIR to the search
path.
The include statement can use full path information, but with the Unix
convention "/" rather than the dos-Windows "\". For example, \include
"..\stuff.ly", with stuff.ly located up one in the tree produces a latex
error "Error invoking `latex \\nonstopmode \\input test.tex > /dev/null 2>&1
'." Change to \include "../stuff.ly" and the error goes away.
========================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
