Re: Long Compile time with version 2.19.44

Hi all, I'm just writing to confirm that under macOS Sierra (10.12) Lilypond 2.19.48 is extremely slow. I've downgraded to 2.19.47 and finally to 2.19.46. 2.19.47 was also terribly slow but 2.19.46 worked as usual. As a sample, a simple file took 1.2 seconds to compile under 2.19.46 and 51.4

Re: status 1 error question

Kieren MacMillan writes: > Hi all, > > The error turned out to be caused by the fact that the lower staff > already contained a rest at the moment where I was [accidentally, via > my \pfUTwo function] trying to also have a sixteenth note g. > > Unless this quick

Re: status 1 error question

Hi David, > With regard to "have not caused problems before": after version 2.19.22, > assertions were enabled for the default compilations. The given > assertion triggers when a definite direction is required but 0 or > #CENTER given. "changing staves/voices" sounds like something where one >

Re: status 1 error question

Hi all, The error turned out to be caused by the fact that the lower staff already contained a rest at the moment where I was [accidentally, via my \pfUTwo function] trying to also have a sixteenth note g. Unless this quick mention/report turns out to be interesting to the developers in terms

Re: status 1 error question

Kieren MacMillan writes: > Hello all, > > Until a few minutes ago, my score was compiling fine (2.19,46). Now I > am getting the following error: > >>

status 1 error question

Hello all, Until a few minutes ago, my score was compiling fine (2.19,46). Now I am getting the following error: > /home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/drul-array.hh:35: > failed assertion `d == 1 || d == -1’ > Exited

Re: applying a tweak or callback to an \after-ed grob

Hi Harm and David, Thank you! >>%% no need for second once, it's already in `hairpinWithCenteredText’ Yes… I’ve altered that now, so that hairpinWithCenteredText is a non-\once \override. (Now that we have \temporary, \single, etc., I think I will make sure that all such functions in my

Re: applying a tweak or callback to an \after-ed grob

Thomas Morley writes: > Or transform the override into a tweak: > > test = { > %% no need for second once, it's already in `hairpinWithCenteredText' > \hairpinPoco g1\< g\! > \after 2 \single \hairpinPoco \< g1 g\! > } > > \score { \test } Hoisted by my own

Re: applying a tweak or callback to an \after-ed grob

Kieren MacMillan writes: > Hi all, > > I’ve been using David K’s lovely \after function (which should, IMO, be > polished up and rolled into the distro!) to great effect in my recent > engravings. > > However, I’m having difficulty figuring out how to apply

Re: applying a tweak or callback to an \after-ed grob

2016-10-08 20:02 GMT+02:00 David Kastrup : > Kieren MacMillan writes: > >> Hi all, >> >> I’ve been using David K’s lovely \after function (which should, IMO, be >> polished up and rolled into the distro!) to great effect in my recent >> engravings.

Re: applying a tweak or callback to an \after-ed grob

Kieren MacMillan writes: > Hi all, > > I’ve been using David K’s lovely \after function (which should, IMO, be > polished up and rolled into the distro!) to great effect in my recent > engravings. > > However, I’m having difficulty figuring out how to apply

applying a tweak or callback to an \after-ed grob

Hi all, I’ve been using David K’s lovely \after function (which should, IMO, be polished up and rolled into the distro!) to great effect in my recent engravings. However, I’m having difficulty figuring out how to apply tweaks to the grobs that are \after-ed. For example, see the snippet

Re: BendSpanner-engraver

Il giorno mar 4 ott 2016 alle 10:37, Thomas Morley ha scritto: Thanks Harm, indeed it's faster. These are the times I got in 5 (small) pieces: 1st version --> 2nd version 2,2" --> 1,8" 2,3" --> 2,1" 3,3" --> 2,3" 2,0" --> 1,7" 1,7" --> 1,5" On my not so