Aloha.
Well, when I do that search I just get back the \include page
(https://lilypond.org/doc/v2.24/Documentation/notation/including-lilypond-files).
So, the answer is no. However, one has to consider the issues of
web-caching interfering with search results.
Within the LP docs I wouldn't have thought to quote the string,
initially, but that doesn't work either; at least not for me as I get
'no reults found'. I might have tried \#f, '#f', "#f", for example, but
generally don't do exhaustive things if the 'natural' one doesn't work;
depends on how crazed I am at the time about solving.
At any rate, I'm open to advice, opinion, suggestion or willing to just
move on.
J.
On 1/8/24 09:31, Kieren MacMillan wrote:
Hi John,
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.
If you do a web search for
lilypond "#f"
is the very first hit not sufficiently helpful?
Cheers,
Kieren.
______________________________________________
My work day may look different than your work day. Please do not feel obligated
to read or respond to this email outside of your normal working hours.
--
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
