On Thu, 22 Jun 2017 06:39:08 +0200, David Kastrup <[email protected]> wrote:
> I don't really see this as calling for changes. If you want to create > utility files to be included at most once, you can try working with > guards like it is customary for C/C++ include files. I think we're shifting topic here from recursive include to multiple include. The latter is general practice. The OP is unintentional infinite recursive includes, and whether LP can help signalling this instead of just becoming non-responsive. Maybe it is possible to track include depth, and issue a (one) warning when the include dept exceeds a certain threshold (20? 50? 100?). -- Johan _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
