On Fri, 2016-11-18 at 21:40 +0100, Thomas Morley wrote: > 2016-11-18 20:36 GMT+01:00 David Sumbler <[email protected]>: > > > > I have a bar which contains 3 notes, e.g. > > > > fs4 ds as' | > > > > It comes after a passage which is pizzicato, but the 2nd and 3rd > > notes > > of this bar need to be arco. However, a normal "arco" marking over > > the > > d sharp does not make it sufficiently clear that that is what is > > intended: particularly because of some earlier passages, a player > > might > > easily think that the arco applies only to the 3rd note. > > > > So I have a marking > > > > larco = \markup { \larger \italic "┌ arco" } > > > > The extra character is intended to make it clear that the 2nd note > > of > > the bar has to be played arco. In order to do that, the mark needs > > to > > be moved to the left so that the little bracket clearly includes > > the > > note, rather than pointing directly to it. > > > > So that bar is now > > > > fs4 \once \override TextScript.self-alignment-X = #-0.6 ds^\larco > > as' | > > > > This works well. > > > > My question is this: is there some way to include the position > > override > > or a tweak within the definition of "larco", so that I don't have > > to > > add it separately every time I use the marking? > > > > I have tried a number of experiments with this, but so far I > > haven't > > figured out how to get it to work. > > > > David > > > > > Hi David, > > there are many possibilities, here two of them > > larco = \tweak self-alignment-X #-0.6 -\markup { \larger \italic "┌ > arco" } > > { > f4 d^\larco a' > } > > larcoII = \markup { \translate #'(-0.8 . 0) \larger \italic "┌ arco" > } > > { > f4 d^\larcoII a' > } > > Both could be turned into a function with argument(s) for the amount > of moving and the markup itself. > Probably even an automagically procedure could be set up to take the > extent of the NoteColumn into account, which is ofcourse variable, > with respect to suspended NoteHeads and Accidentals. > > Cheers, > Harm > > P.S. Please post always a minimal and _compilable_ example, including > the LilyPond-version you use.
Thanks for that. I see now that this is to some extent related to a question I asked a couple of weeks back, which you kindly answered. Again I was omitting a "-" where one is needed: in this case, before the \markup if the tweak is placed before it. I need to study this (and the previous answer) to see if I can fathom out the logic of it all. The solution with \translate is simpler, of course - I should have discovered this method for myself, but stupidly it didn't occur to me that there might be such an easy way to move markups around. David _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
