Re: [Lilypond-auto] Issue 3140 in lilypond: Patch: Move Timing into separate context

[lilypond]

Comment #6 on issue 3140 by address@hidden: Patch: Move Timing into separate  
context
http://code.google.com/p/lilypond/issues/detail?id=3140

Looks like with an actual Timing context created, LilyPond considers it  
fair game for a Bottom context and does not bother to create an implicit  
Voice, instead feeding everything to Bottom.

Disentangling that seems rather ugly.  So it might be smarter to stick with  
aliases to existing contexts, and the simplest way is to move the Timing  
alias and the associated variables up to Global, since Global always  
exists.  The other possibility is to somehow enforce Score being created  
automatically (and then have its alias take over) when doing \set  
Timing.xxx = whatever.  But that does not really appear cleaner.

One ickiness is the number of timing-related variables that need to be  
copied.  It might be a nice idea to just copy an entire Timing context, but  
that does not work when Timing is an alias to some context containing a lot  
more than timing variables.