Please "reply all" to keep your reply on the mailing list.
If you simply try this out, you will find that \include-ing a file simply
effectively replaces the \include filename with the contents of the file. So
most of the files need have nothing more than the text you want to include. Go
ahead - try it out!
--
Phil Holmes
----- Original Message -----
From: Nikolai Hedler
To: Phil Holmes
Sent: Tuesday, June 11, 2013 5:07 AM
Subject: Re: "form" file using \include (or not?)
I get how to use \include in a file, at a basic level, but the question is if
there's a way to have separate files that contain the music and identifying
information, but don't need to have all of the standard parameters that I use
on every one of my files, e.g. margins and \midi { }, etc. Can I just stick
those all into a file and \include that file? Some of that stuff has to go into
different places within the file, no?
On 10 June 2013 14:35, Phil Holmes <[email protected]> wrote:
http://lilypond.org/doc/v2.16/Documentation/notation/including-lilypond-files#index-including-files
--
Phil Holmes
----- Original Message -----
From: Nikolai Hedler
To: [email protected]
Sent: Monday, June 10, 2013 7:30 PM
Subject: "form" file using \include (or not?)
Is there a way that I can create a template file that I can \include
which has a layout and basic parameters which are common between my scores?
Alternatively, since I use jEdit, is there something I can append to the
compile command that would achieve the same thing? The idea here is that I
would be able to create a file which contains the music, that I could e.g.
\include (as a part) in a score, but could still compile individually to create
a single part.
Is there a common practice to achieve that outcome? Any assistance would
be appreciated.
--------------------------------------------------------------------------
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
