Hi,
obviously, LilyPond gets confused when the version string contains
more than dots and numbers.
This is a defect IMHO.
Regards,
Marc
-------- Original-Nachricht --------
Betreff: Re: Non-customary clef printing
Datum: Fri, 31 Jan 2014 10:11:45 +0100
Von: David Kastrup <[email protected]>
An: Marc Hohl <[email protected]>
Kopie (CC): [email protected]
Marc Hohl <[email protected]> writes:
Hi David,
Am 30.01.2014 07:18, schrieb David O'Donnell:
I am trying to replicate an older score, where the the clef changes at
the beginning of the line. However, unlike Lilypond's default, the old
clef and the key signature are printed and then immediately following
that, the new clef is printed before any notes appear.
There is a snippet which shows how to do this at the beginning of a
piece (http://lsr.dsi.unimi.it/LSR/Item?id=792), but I can't see how to
do it mid-piece.
I even tried inserting a dummy note to do a clef change mid-measure, but
that makes an unsightly gap between the key signature and the new clef.
First of all, please provide compilable examples! I got a segfault on my
machine trying to compile your attachment.
The version statement "2.18.0-1" is the culprit.
A segfault does not really sound like a commensurate error diagnostic
for a malformed version string. Seems like this would warrant an issue
report.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
