David Kastrup <d...@gnu.org> writes:
> thomasmorle...@gmail.com writes:
>
>> I then would have expected the following to work (with a warning):
>>
>> { \voicify 1 << a' \\ c' >> }
>>
>> instead I get:
>>
>> $ lilypond-git atest-54.ly
>> GNU LilyPond 2.19.59
>> Processing `atest-54.ly'
>> Parsing.../home/hermann/lilypond-git/build/out/share/lilypond/current/scm/music-functions.scm:978:31:
>> In expression ("No more voicification ids"):
>> /home/hermann/lilypond-git/build/out/share/lilypond/current/scm/music-functions.scm:978:31:
>> Wrong type to apply: "No more voicification ids"
>
> This so is a bug, looks like trying to call a string as if it were a
> function. I'll take a look what I did wrong here: thanks for spotting
> it!
Oh good grief. After fixing that, voicify-item actually gets a list to
work with and can't use ly:music-warning, and that list can be empty.
Getting good error messages is apparently a bit harder than I thought...
>> https://codereview.appspot.com/320820043/
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
