Noeck writes:
> The idea that included files are indistinguishable from copy-and-paste,
> even goes to extreme levels. This works:
>
>
> --- included.ly
> title = "title"
> composer = "composer"
> }
> --
>
>
> --- main.ly
The idea that included files are indistinguishable from copy-and-paste,
even goes to extreme levels. This works:
--- included.ly
title = "title"
composer = "composer"
}
--
--- main.ly
\
On 02.08.2018 10:43, Peter wrote:
Thanks Simon yes sometimes I am not sure what environment the
interpreter is in, especially when it is expecting a music
Element or not. It's obvious in the simple case but can be confusing
in a more (unessessaryily?) complex file.
With variable definitions it
On 23.07.2018 16:22, Peter Gentry wrote:
It looks as though in this case the compiler is treating each
"addTextSpannerText.ly" in the parts as music rather than scheme.
\include acts in a way that is completely indistinguishable from just
pasting the content of the file instead of the include.
I have placed a copy of addTextSpannerText.ly to the C:/Program Files
(x86)/LilyPond/usr/share/lilypond/current/ly folder.
My score has five parts and in case a. each part/movement file includes the
statement - \include "addTextSpannerText.ly"
Result - Each part/movement compiles without error.
David wrote You can. It's just a matter of describing "anywhere" in terms a
computer can understand.
Very true the only weak link is “in terms the less than adept user can
understand”
😊
___
lilypond-user mailing list
lilypond-user@gnu.org
h
"Peter Gentry" writes:
> I was amazed at how complex this simple common problem turns out.
>
>
>
> I have used the rather complex scheme code from the archives but there
> remain problems when spanning rest bars.
>
>
>
> You would think this is a common requirement. Why can't you place any t
