Another bug fix version, and this is the first version ever with a code name — definitely an apt one. It only fixes command line invocation with LilyPond 2.12.x. So this fix need not be applied if lilypond is not used, or LilyPond inside server is not newer than 2.10.x release.
Why the name? I haven’t used LilyPond for a long while. Only very recently, after testing compatibility with newer WordPress release, did I discover that LilyPond safe mode command line option is completely gone, resulting in error! There IS a reason even Wikimedia people cast doubt about usage of LilyPond — notation syntax and command line can change between every minor release, and even EVERY PATCH LEVEL! In the case of safe mode option:
| 2.8.x | --safe |
|---|---|
| 2.10.x | --safe-mode |
| 2.12.x | -dsafe |
Go figure.
2010-02-26: OK, so the safe mode option in 2.12.x is there after all, I haven’t followed Lilypond development for a long while so don’t even notice that. It’s -dsafe now. Thus in 0.3.3 version safe mode is re-enabled. Sigh.









