Re: [Lilypond-auto] Issue 2935 in lilypond: Issue 2859 (Provide \hide and \omit functions) breaks -dsafe option

[lilypond]

Updates:
        Owner: address@hidden

Comment #2 on issue 2935 by address@hidden: Issue 2859 (Provide \hide and  
\omit functions) breaks -dsafe option
http://code.google.com/p/lilypond/issues/detail?id=2935

Well, it is a regression, but it is not "critical" in that it does not  
(yet) concern any stable version/release.  The named commit pretty  
certainly is not guilty: it would appear that git bisect was not run  
correctly here.

That does not mean that I claim innocence: I am pretty sure that the fault  
will like with
commit 9eb1eba8423cdd66f7bb0e51cb1b6104fe4e3019
Author: David Kastrup <address@hidden>
Date:   Mon Oct 1 14:15:17 2012 +0200

    Issue 2872: Provide define-session and define-session-public commands

    Also moves the session logic into lily.scm instead of init.ly

    A session corresponds to one .ly file on the LilyPond command line;
    sessions are supposed to be processed independently in one LilyPond
    run.

    define-session will declare a variable that has its value recorded at
    the start of the first session and reinstated at the start of each
    following sessions.  This is automatically the case for every variable
    defined in variables in the parser module established while loading
    ly/declarations-init.ly.  However, not every changeable information
    handled in the .scm parts of LilyPond can easily or reasonably be
    stored in the parser module.  define-session (and
    define-session-public) provide a way to get the same semantics for
    variables defined in the Scheme parts of LilyPond.

If you could corroborate that you can see the fault appear with this  
commit, this would be helpful.  I'll be likely looking at it tomorrow since  
I need to get a few other urgent tasks related to 2.16 done first, and it  
would be good to know that my guess about what needs fixing is not mistaken.

Thanks!