On 12/16/12 at 12:04pm, Glen Larsen wrote: snip > like the header are regular enough that they can be parsed easily. If only > lilypond had, in addition to the --header switch, a switch that would exit > after the parse phase; as you mentioned, it simply takes too long to get a > single header value. Except in pathological cases, the parsing can be > scripted in python easily enough.
I just played a bit more around and found a way to get lilypond to output header fields just after parsing by inserting some scheme code at the end of the file. Attached is a proof-of-concept script for retrieving the composer name (use it like "sh composer.sh file.ly"). Felix
composer.sh
Description: Bourne shell script
_______________________________________________ Mutopia-discuss mailing list [email protected] http://lists.bcn.mythic-beasts.com/mailman/listinfo/mutopia-discuss
