Re: [Lilypond-auto] Issue 2558 in lilypond: Documentation suggestion: Including LilyPond files

[lilypond]

Comment #4 on issue 2558 by address@hidden: Documentation  
suggestion: Including LilyPond files
http://code.google.com/p/lilypond/issues/detail?id=2558

I'm having a little trouble convincing myself that
setting relative-includes off is actually helpful.
For example, Urs says

> For example:
> - If I have a general library
>    I will want to have relative-includes on
> - But if I have normal include files (e.g. music definitions)
>    I will want to have relative-includes off
>    because these files reside in files relative to the main .ly file

but if the local files are relative to the main .ly file
leaving relative-includes on will work just as well.

Also, it is the intention to switch the default value to #t,
and I would suggest switching at the start of or early in the
2.17 cycle would be sensible.  If people agree, this section
will need a (small) rewrite anyway.

I'll wait to see if there are any other suggestions, but my
inclination at the moment is to mark this invalid.

Trevor