|
From: | Eluze |
Subject: | Re: \\bookOutputName not working if a \\paper block uses a previously defined variable |
Date: | Mon, 26 Mar 2012 02:10:52 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0 |
Am 25.03.2012 23:50, schrieb David Kastrup:
I found this weird expression in the docs - other forms are not mentioned. I will gladly apply the simple form now!Eluze<address@hidden> writes:Am 25.03.2012 19:35, schrieb David Kastrup: Personally, I think it would make more sense if people just placed assignments to output-filename and output-suffix inside of the book's paper block. That's straightforward to understand and does not require keeping magical ordering relations in mind. \bookOutputName is more like a compatibility API. A courtesy to keep around, but not as straightforward in its implications. this works: bigMargin = \paper { top-margin = 10 \cm } \book { \paper { \bigMargin #(define output-filename "output-filename") } \relative {c d e f} }Ugh. Why don't you write \paper { \bigMargin output-filename = "output-filename" }
putting the assignment before \bigMargin still produces an error and the output returns to default.this not (because of the order): \book { \paper { #(define output-suffix "output-filename") \bigMargin } \relative {c d e f} }Hardly surprising now, is it, if you write it as _assignment_ rather than as some weird Scheme block?
output-suffix is mentioned in Usage, Snippets and NR; output-filename can not be foundI was not suggesting that the documentation was already in a useful state. Rather I was suggesting _how_ we should preferably fix it.
we're on the way, aren't we!? Eluze
[Prev in Thread] | Current Thread | [Next in Thread] |