[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What's the idea with the $papers stack?
From: |
Han-Wen Nienhuys |
Subject: |
Re: What's the idea with the $papers stack? |
Date: |
Sat, 14 Dec 2013 20:59:03 +0100 |
On Sat, Dec 14, 2013 at 6:32 PM, David Kastrup <address@hidden> wrote:
>
> The only place where it is "pushed" is when creating a _new_ book, and
> then it is cleared out immediately before it. What kind of pushing is
> that supposed to be? What does that even mean? A paper block in a book
> definition manipulated the top book entry, except when looking at a book
> identifier. So the following crashes:
>
>
>
> Does anybody have a clue what the $papers stack is supposed to be for?
> When accessing paper variables, LilyPond looks through that "stack".
> That's where things like book-specific filenames will be kept.
Output definitions (paper, bookpaper) are nested so you can set global
layout at book level, and still have per-movement overrides. Stacking
N output definitions is as much work as stacking 2, so I guess I made
it generic.
Of course, few people if any ever used this feature.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen