As you can guess, that's the logfile produced when lily runs multiple jobs
simultaneously. It also produces logfiles called something like multicpu0.log
- look in the same directory for these - they'll have the most recent
timestamp, too.
Phil Holmes
- Original Message -
From:
Looks quite plausible; please push directly to staging.
http://codereview.appspot.com/5938048/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM; since it's just a snippet now, I support pushing it directly as
long as it compiles.
http://codereview.appspot.com/5882053/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM,
but if the solution is to avoid looking at the stem extent, then there
is another case to solve with tremolo flags
{ \aikenHeads f'4:32 } \\ { \aikenHeads f' }
and then beams
{ \aikenHeads e'8 f' s4 } \\ { \aikenHeads e'8 f' s4 }
...
