Re: layout-set-staff-size: will it ever be fixed?

[Nikolai Hedler]

I see that this may have been worked on in 2.19 as Issue 216; can someone update me as to the current status?

On 23 March 2015 at 16:47, Nikolai Hedler <address@hidden> wrote:

On 23 March 2015 at 16:40, Kieren MacMillan <address@hidden> wrote:

Hi Nikolai,

> Is there any reason not to fix a known bug that's been around for this long that's been a pain in the neck since I started using LilyPond?

If you don’t see any reason, then please send in a patch for review.

How would I do this? I assume that by this you mean that I should fix it myself, which I would if I knew anything about how LilyPond is coded, but I'm a full-time student, and as such can't really afford to take the time to teach myself all about it. The main purpose of this is to inquire as to any reason why it hasn't been addressed already. 

> My goal is to be able to create a single file which outputs a book including a score and all parts, where the score is staff-size 15 and the parts are 18 or 20

I do that exact thing all the time.
While more syntactic sugar would certainly make it even easier, I've never found it to be a particular pain in the neck.

Would you like to enlighten me, then? Or do you mean to recommend that I just use the hackish workaround?

Thanks,

Nikolai Hedler