lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Snippet variations


From: Br. Samuel Springuel
Subject: Re: Snippet variations
Date: Sat, 17 Dec 2016 10:41:28 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1

I have never worked with TeX and its relatives, so my only experience is in
plain LY files.

For those not familiar with lyluatex, the way I'm using it works as follows:

1) Inside a the TeX file there is a pointer to the lilypond source file of the snippet I want to include.

2) When LuaTeX processes the document, it looks at the file indicated by the pointer and looks to see if there existing, up-to-date images of that snippet.

3) If LuaTeX cannot find existing, up-to-date images, then it runs lilypond on the the source.

4) The up-to-date images are then included in the document in the location where the file pointer was specified.

If every snippet consists of a LY file of its own, it could contain a
statement like
    \include "aster-def.ily"
If you change the contents of the latter, the change applies to all
snippets.

If the snippets themselves are to be used as include files to be called in a
"master" document, you can start this document with the aster definition of
your choice, followed by the \include statements of the snippets.
I use this method very often.

In a sense, both of these conditions are true. Each snippet has its own LY file and they are all being included in a master document, it's just that the master document is a TeX document, not a LY one.

Further, I need to use both versions of the snippet in the same document. As a result, I cannot just change the LY source when I want one or the other, I have to be able to get both out at the same time.

Adapting what you suggested, then, it seems that I might be able to do the following:

1) have the snippet source which doesn't contain the \aster definition
2) have two different include files, one with \aster defined to insert the `*`, the other with it defined to do nothing 3) have two "top-level" files which include one of the \aster definition files and the snippet source 4) in the master document, point to the "top-level" file which corresponds to the version of the snippet which I want in that location


That seems like a fairly reasonable solution, unless some one out there has a better one.
--
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
St. Anselm’s Abbey
Washington, DC
(R. Padraic Springuel)

PAX ☧ ΧΡΙΣΤΟΣ



reply via email to

[Prev in Thread] Current Thread [Next in Thread]