Peter Chubb wrote:
"Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:


Han-Wen> [EMAIL PROTECTED] writes:

I have a latex file containing fragments of lilypond code.  It
includes other files using

\include{file}

lilypond-book doesn't ever match this construct --- for some reason
it's looking for

\mbinclude{file>


Han-Wen> \include{} is a latex macro that also does other stuff
Han-Wen> (insert a line break, iirc). For this reason, we don't
Han-Wen> process \include{}.

\include{} inserts a pagebreak, actually.

This behaviour (ignoring \include{}) confused me, because the BUGS
section only mentions that \includeonly{} doesn't work --- implying to
me that regardless of what \includeonly{} says, all \include{}
directives are honoured.

I can't see any problem of supporting \include (with the exception of the limitation currently mentioned in the docs). Lilypond-book just has to treat \include and \input by copying the directive to the generated .latex file and then calling lilypond-book recursively (at least conceptually) on the file to input. I think I saw patch sent to the list some weeks ago that did this.

/Mats




_______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to