[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Identify included files
From: |
Fr. Samuel Springuel |
Subject: |
Re: Identify included files |
Date: |
Sat, 16 May 2020 15:39:11 -0400 |
> On 15 May, 2020, at 5:04 PM, David Kastrup <address@hidden> wrote:
>
> "Fr. Samuel Springuel" <address@hidden> writes:
>
>> Before I start writing a script to do this, is there an existing tool
>> which will identify all the `\include` files that a LilyPond file
>> depends on? Even better, one that will work in a recursive fashion?
>
> You can use a file like
>
> ...
> and call it with
>
> lilypond --init parse-only.ly actual-file-name.ly 2> /dev/null
>
> and it should be pretty fast. Of course the file list includes
> parse-only.ly...
>
>
> --
> David Kastrup
Very nice. I’ve tested the various options and this seems to be the best
option. While I haven’t tested with a really big file, this option appeared to
be independent of file size while the option I came up with isn’t.
Is there any chance that something like this could be introduced into LilyPond
core?
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Fr. Samuel, OSB
(R. Padraic Springuel)
St. Anselm’s Abbey
4501 South Dakota Ave, NE
Washington, DC, 20017
202-269-2300
(c) 202-853-7036
PAX ☧ ΧΡΙΣΤΟΣ
- Re: Identify included files, (continued)
- Re: Identify included files, David Wright, 2020/05/23
- Re: Identify included files, Fr. Samuel Springuel, 2020/05/22
- Re: Identify included files, antlists, 2020/05/18
- Re: Identify included files, David Wright, 2020/05/18
- Re: Identify included files, Urs Liska, 2020/05/18
Re: Identify included files, David Kastrup, 2020/05/15
- Re: Identify included files,
Fr. Samuel Springuel <=