Re: bizarre behaviour of `output-filename`

[Dan Eble]

On Oct 21, 2023, at 01:12, Werner LEMBERG <wl@gnu.org> wrote:
> 
> 
> 
>>> Some debugging shows it seems to be the latter: All top-level
>>> definitions are available as paper variables within a book's paper
>>> block, together with all paper variables of the top-level paper
>>> block:
>>> 
>>> Is this really intentional?
>> 
>> https://gitlab.com/lilypond/lilypond/-/issues/5917
>> https://codereview.appspot.com/567450043
> 
> Really?  I would never have expected that this quite innocent-looking
> patch makes top-level definitions (outside of any block) available as
> paper variables within `\book`.  The comment in `book.cc` only talks
> about `\header` blocks.  How does this influence stuff outside of
> `\header`?  And how does it influence `\paper`?
> 
> In case this patch is really the cause, can the behaviour be
> restricted to `\header` blocks as announced in the commit message?

I might have been mistaken.  I don't have much time to give to LilyPond these 
days.
— 
Dan