[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 2536 in lilypond: Patch: Make \footnote work v

From: lilypond
Subject: Re: [Lilypond-auto] Issue 2536 in lilypond: Patch: Make \footnote work via \tweak
Date: Wed, 16 May 2012 19:51:33 +0000

        Labels: -Patch-needs_work Patch-new

Comment #3 on issue 2536 by address@hidden: Patch: Make \footnote work via \tweak

Make \footnote work via \tweak

Allow Tweak_engraver to take a ( pair as tweak address

Revert "Merge branch 'footnote' into HEAD"

This reverts commit 2ec0cd55d55c49dee4e5604903dfab8ff4a089c4, reversing
changes made to 0a0274a3bf5792dfb7ce3719f5dfaef36059affe.

Those are the three commits currently making up this issue.  The music
function \footnote, in addition to the arguments it already takes, now
takes an additional music argument, either a chord constituent, or a
music event on its own, or a postevent (in which case, like \tweak,
you should invoke \footnote with an explicit event character - in
front of it).  The footnote is visible on any Grob directly caused by
the following event in the source code (the additional music
argument), unless a grob-name is specified, in which case it will
appear on any grob of that type _ultimately_ caused by the following
event (a Flag is directly caused by a NoteHead grob, but ultimately by
a NoteEvent).

I had been considering placing the anchoring Music event as first
argument of \footnote.  However, that makes for totally awful nesting
syntax in case you attach several footnotes to the same Music.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]