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

[lilypond]

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

I think this has to be rethought a little bit (right now I don't have an  
opportunity to really sort this out, so I'll just drop a few hints to be  
picked up later):

The paragraph starting with
"Files which are to be included can also contain ..." gives the impression  
that #(ly:set-option 'relative-includes #t)
is a decision to be made before compiling a score.

But in fact you can place the function at any place in the score, even  
multiple times and switch back and forth between the two behaviours.

This may be extremely useful.
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

With the possibility of switching behaviour I can have both at the same  
time, i.e.
- include a library (which has relative-includes set on) and
- afterwards include 'local' files
Or I can have include references to 'local' files in a 'general' library.

I think the relevant doc section should be changed quite fundamentally to  
explain this function more thoroughly