Re: [Lilypond-auto] Issue 3126 in lilypond: Fails to return a book created inside #{..#} substitution music function

[lilypond]

Updates:
        Status: Fixed
        Owner: address@hidden
        Labels: Fixed_2_16_3

Comment #1 on issue 3126 by address@hidden: Fails to return a book created  
inside #{..#} substitution music function
http://code.google.com/p/lilypond/issues/detail?id=3126

I've pushed the maininput/EOF related changes to stable/2.16 now, so they  
should appear in the next release.  They appear to do the trick with this  
example.
commit 9eaaaf76ec4fefd042b81045ca33c4fd487ece4c
Author: David Kastrup <address@hidden>
Date:   Fri Jan 11 23:20:40 2013 +0100

    Issue 3102: Allow EOF to occur in the middle of a line comment

commit 844ada8686c70851b53529b28284c39780dbe5fd
Author: David Kastrup <address@hidden>
Date:   Sun Dec 23 22:13:08 2012 +0100

    Make lexer more robust against unexpected EOF

    This helps against EOF within strings, multiline comments and other
    constructs without losing track when terminating the main input parser
    while retaining the lexer.

    Conflicts:
        lily/lexer.ll

commit 9e580cb439a9379a9f32340ce7594b57e7e325b8
Author: David Kastrup <address@hidden>
Date:   Wed Oct 31 12:33:15 2012 +0100

    Issue 2939: Fix relations between \maininput, EOF and safe mode

    In lexer.ll, assumptions about the depth of include_stack_ were  
hardwired
    that only were valid for parsers started from the normal chain of input.

    One consequence was that something like

        #{ \book { \include "line-arrows.ly" } #}

    worked even in safe mode (where \include should be prohibited) but
    might complain about unexpected EOF.  This commit adds a member
    variable main_input_level to Lily_lexer for keeping track of when to
    drop restrictions and deliver EOF in each parser separately.

commit 6362ea7c8257fa4ce740eaa66430f6f0d263d29c
Author: David Kastrup <address@hidden>
Date:   Tue Oct 30 11:17:22 2012 +0100

    Issue 2935: is_main_input_ should only be set by \maininput command

    is_main_input reflects the state of being in the reign of the main
    input file as opposed to the init file, which corresponds to a drop of
    privileges.  This drop of privileges is explicitly signified with

    \maininput

    and should not otherwise be tampered with in order not to restrict the
    init file's capabilities.  There should be no way to arrive at a lexer
    from within LilyPond or Scheme without is_main_input_ set unless one
    already has one such lexer to start with.