Re: improving Janek's \dynamic function (for combo dynamics)

2017-08-19 Thread Shevek
I posted a snippet to do correct custom dynamic alignment a month or so ago. I haven't had time to integrate it into the OpenLilyLib snippet, but here's my code: \version "2.18.2" dynText = #(define-event-function (parser location dyn expr) (markup? markup?) (let* (

Re: Moving a tempo mark to the right

2017-08-19 Thread Wols Lists
On 19/08/17 15:11, Kieren MacMillan wrote: > Hi Wol, > >> My usual moan about colliding markups :-) > > Given how usual your moans are… ;) > Can I ask why you don't just write a custom function to deal with the various > markups automatically? > It really wouldn't be that difficult, and would

Re: Moving a tempo mark to the right

2017-08-19 Thread Kieren MacMillan
Hi Wol, > My usual moan about colliding markups :-) Given how usual your moans are… ;) Can I ask why you don't just write a custom function to deal with the various markups automatically? It really wouldn't be that difficult, and would reduce the moaning to zero (or nearly). As to your

Lilypond GtkSourceView language definition

2017-08-19 Thread Jean-Philippe Combe
All, After searching for a while it seems that there is no GtkSourceView definition for Lylipong. As a consequence, I start to create a new one by myself. It supports comments, include, strings and keywords (based on the latest Lylipond 2.19 command list)... More informations are on my blog

Re: Moving a tempo mark to the right

2017-08-19 Thread Pierre Perol-Schneider
Hi Anthony, Does that help? \version "2.19" \markup\vspace #5 { s2.*3 s1*8 \bar "||" \tweak outside-staff-priority #0 \mark \default % 111 \tempo "Languidly" %\once \override TextScript.outside-staff-priority = #2000 <>^\markup { %\halign #-1.1 \small "The Last Night Of The

Re: Moving a tempo mark to the right

2017-08-19 Thread arnepe
use the Edition engraver with for e.g. %% example mock-up %% \editionMod markmove 1 0/4 my.test.Score.A \once \override Score.MetronomeMark.extra-offset = #'(2 . 0) cheers Arne -- View this message in context: