Mahalo. Appreciate the input. I understand the \include stuff and am
familiar with the concepts with that added info.
My larger concern is with the ability to find these details with limited
knowledge about LP; as a relative novice. I wrote a longer reply to the
list about this but, in short, I wouldn't have likely found this bit
about #t #f without referrals. Seems I should have been able to search
for them but it didn't succeed. I'd like to help figure out why it
didn't succeed.
J.
On 1/8/24 02:37, Aaron Hill wrote:
On 2024-01-07 11:14 pm, John Helly wrote:
Aloha.
In reading the documentation about \include
(https://urldefense.com/v3/__https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files__;!!Mih3wA!HDjAraGREPu720QX_4rbInA4mBp2q8iZVSzhqWOqPV1rAhmglwXGHkmJgPFkmDaV-3KRfxJByQDrUSMeZdye$
), I find the following sentence but can't find any explanation
anywhere about what *#f and #t *are or do. Can anyone enlighten me,
please? They seem to have something to do with the file system but...?
#t and #f are just the Scheme ways of indicating the Boolean values of
true and false, respectively. So, for a setting like
relative-includes, #t would enable the feature; #f would disable it.
'... Complex file structures, that require to|\include|/both/files
relative to the main directory and files relative to some other
directory, may even be devised by
setting|relative-includes|to*|#f|or|#t|***at appropriate places in
the files. ...'
This part of the documentation is simply indicating that the
relative-includes setting can be freely changed during input
processing as needed. So when you go to \include something, it is the
current setting that will affect where LilyPond will search for the
file in question.
-- Aaron Hill
--
John Helly, University of California, San Diego / San Diego Supercomputer
Center / Scripps Institution of Oceanography / 760 840 8660 mobile /
http://www.sdsc.edu/~hellyj
ORCID ID: orcid.org/0000-0002-3779-0603
