Alexander Kobel <a-ko...@a-kobel.de> writes: > On 2016-11-02 12:01, David Kastrup wrote: >> Alexander Kobel <a-ko...@a-kobel.de> writes: >>>[...] >> Ugh. Maybe it's just \addlyrics then? Or wait: >> >> >> >> >> Uh, what?!? >> >> lilypond /tmp/alex.ly >> GNU LilyPond 2.19.50 >> Processing `/tmp/alex.ly' >> Parsing.../usr/local/share/lilypond/2.19.50/scm/ly-syntax-constructors.scm:294:12: >> In procedure ly:music-property in expression (ly:music-property >> music (quote elements)): >> /usr/local/share/lilypond/2.19.50/scm/ly-syntax-constructors.scm:294:12: >> Wrong type argument in position 1 (expecting Prob): "sop" >> >> Uh, this looks like the parser actually knows how to deal with the >> syntax as such but it royally messes up doing something useful with the >> parsed results. >> >> Well, it has been nice talking about this. Let's continue this >> discussion in a week or so. > > Sure. ;-)
This syntax was added in commit df3457d85ebfa4bc347a4569241227449f84b901 Author: David Kastrup <d...@gnu.org> Date: Tue Sep 9 11:14:34 2014 +0200 Allow \addlyrics to work with arbitrary contexts No mention of \lyricsto, no mention of the issue number in the commit message, obviously no regtest for the \lyricsto part of the syntax change. Wish there were somebody else to rant at. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user