Thanks both.
I doubt this feature is needed with any frequency. I happen to be leveraging some orchestral LP code, which is proving quite convoluted to trace with its many nested \include’s and needs upgrading to current version.
Some compile issues were reported as programming errors in 2.18.2 with no clear indication of an associated line of code.
I’m down to one remaining error:
“programming error: Improbable offset for stencil: -inf staff space”
Seems to be associated with the following scheme function:
#(define (not-last-page layout props arg)
(if (not (book-last-page? layout props))
(interpret-markup layout props arg)
empty-stencil))
The function is used to generate custom on-the-fly footers for pages other than first and last.
I need to create a separate tiny example to replicate and isolate where the issue is coming from. I’ll ask for help in a new thread.
Javier
From: Simon Albrecht [mailto:address@hidden
Subject: Re: Way to flatten nested \include's?
Am 23.08.2015 um 15:23 schrieb Knute Snortum:
I don't know of a LilyPond way to do this, but it would probably be a fairly simple Python or Perl program.
And wouldn’t it be user-friendly to provide such a script with our default binaries, that is alongside convert-ly?
My 2cts, Simon
On Sat, Aug 22, 2015 at 2:20 PM, Javier Ruiz-Alma <address@hidden> wrote:
I have code split into multiple files.
Is there a way to ask lilypond to expands nested \include's and dump into new file, such I can review/compile a flattened version of the code (i.e. for debugging)?
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user