Re: Issue 2024 in lilypond: Patch: Let #{ ... #} pass its $ handling to environment cloning

[lilypond]

Comment #12 on issue 2024 by address@hidden: Patch: Let #{ ... #} pass its $  
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024

Uh, the # syntax is not old, it is different in meaning (namely
auto-exporting).  I should definitely hope that display-lily-music would
not create $ gratuitiously.

Since set-time-signature does no longer export itself, display-lily-music  
indeed produces wrong syntax (I think it is hardwired what it produces for  
a given output, and not related to what input will in reality produce the  
output).

I don't think I'll bother fixing this; instead I'll try tomorrow to create  
music function versions of the five ugly-syntax functions, and then change  
display-lily-music accordingly.  It's probably saner to do this in one  
iteration of convert-ly instead of generating an intermediate state.  This  
will still be done for automated conversion (like in Baerenreiter regtest)  
since conversion into music functions can't be automated: you need to  
figure out proper argument list types.