> On May 25, 2020, at 2:58 AM, Wols Lists <antli...@youngman.org.uk> wrote: > > On 24/05/20 21:28, Fr. Samuel Springuel wrote: >> It’s not quite as straight-forward as you seem to think: >> >> 1) You haven’t accounted for the possibility of multiple folders with >> varying levels of hierarchy. The changed file might be in ../ relative to >> one file, ../../ relative to another, ../some/dir/levels relative to a third >> and other possible variations. It might also be specified >> /with/an/absolute/path in some files. All of that complicates the search >> string for grep. > > This is a real can of worms ... > > I THINK all paths are relative to where lilypond is running. So any > include file that itself contains relative includes is asking for > trouble - it's "random" whether those paths will be valid or not... > > Cheers, > Wol >
It depends on the state of the relative-includes variable. If true, then paths are relative to the file in which the include statement appears. If false, the paths are relative to the main input file. Default behavior is false. It’s explained here: http://lilypond.org/doc/v2.21/Documentation/notation/including-lilypond-files
