[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) cont
From: |
Ian Hulin |
Subject: |
Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) context property |
Date: |
Tue, 26 Jan 2010 23:12:05 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 |
Hi Vincent,
On 24/01/10 19:39, address@hidden wrote:
Updates:
Summary: [in progress] output-suffix as a (Score) context property
Cc: Carl.D.Sorensen
Labels: -Priority-Low Priority-Medium Patch
Comment #3 on issue 836 by v.villenave: [in progress] output-suffix as a
(Score) context property
http://code.google.com/p/lilypond/issues/detail?id=836
Where are we with regard to this issue? I've been grepping through the
git-log
without finding anything related to Ian's work. I hope nothing has been
lost/forgotten here.
In the end I had to resort to using new functions to do this rather than
contexts, since contexts seem to reserved for the music translation
process in Lilypond, and these properties refer to 'contexts' that
reference an environment way before we're translating the text to grobs
appearing on paper.
I'd started off assuming Lilypond was using objects and properties in a
generalized OOPS way and we were setting properties regarding the
compilation unit, hence my questions about book blocks and contexts.
If anyone thinks it would be more consistent an a worthwhile use of my
time to have these things done as
\score {
output-suffix = "movI"
.
.
.
}
or
\score {
output-file = "MyGrandOpus"
.
.
.
}
I'm willing to continue working on this.
Maybe this is the kind of discussion for GLISS?
Cheers,
Ian