Re: Extend all hairpins over time signature changes

2021-03-01 Thread Kieren MacMillan
Aaron, > So it just the case that you want hairpins to extend over time signatures? A > custom engraver could automate that: THIS IS GOLD! Thanks, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email:

Re: Extend all hairpins over time signature changes

2021-03-01 Thread Aaron Hill
On 2021-03-01 2:39 pm, N Trocado wrote: Thank you for your answer. I do use /once when appropriate, and defining a variable indeed helps with the typing. But I was hoping for a way of establishing that all hairpins that cross time signature changes extend beyond the barline, and if lilypond took

Re: Extend all hairpins over time signature changes

2021-03-01 Thread N Trocado
Thank you for your answer. I do use /once when appropriate, and defining a variable indeed helps with the typing. But I was hoping for a way of establishing that all hairpins that cross time signature changes extend beyond the barline, and if lilypond took care of this automatically it would be

Re: Extend all hairpins over time signature changes

2021-03-01 Thread Aaron Hill
On 2021-03-01 9:52 am, N Trocado wrote: I like to have hairpins cut through barlines, extending to the note that ends them on the first beat of the next bar, whenever there's a time signature change. Stopping short of the barline in this case, as is the default, leaves a bit too much space

Re: Stacked tensions for chord names

2021-03-01 Thread Aaron Hill
On 2021-03-01 7:13 am, Robin Bannister wrote: And if you are fed up with baseline-skip you can set it to 0, and it then stays 0 whatever the font-size. [...] no-bs = #'(baseline-skip . 0) [...] Was there intention behind that variable name? ;-) -- Aaron Hill

Extend all hairpins over time signature changes

2021-03-01 Thread N Trocado
I like to have hairpins cut through barlines, extending to the note that ends them on the first beat of the next bar, whenever there's a time signature change. Stopping short of the barline in this case, as is the default, leaves a bit too much space between the end of the hairpin and the

Re: Stacked tensions for chord names

2021-03-01 Thread Robin Bannister
Valentin Petzel wrote: My problem is that at Position where the markup is defined the fontsize is in fact not known. I’ve solved the issue for the time being by using a on-the-fly call to modify the baseline-skip. You can fetch the font-size with#:properties ((font-size 0)) as done in

Re: Stacked tensions for chord names

2021-03-01 Thread Valentin Petzel
Hello Robin, thank you for your reply. The problem here is that \fontsize is never called. The font-size is entirely handled by the grob callback ly:text-interface::print. My problem is that at Position where the markup is defined the fontsize is in fact not known. I’ve solved the issue for

Re: Request for a stencil alignment helper

2021-03-01 Thread Dimitris Marinakis
Thank you Aaron! This is exactly what I needed. On Sun, Feb 28, 2021 at 5:21 AM Aaron Hill wrote: > On 2021-02-27 3:55 pm, Dimitris Marinakis wrote: > > Is it possible to make a "stencil-wrapper" that will show the vertical > > centre of a stencil and have an extending line of variable length >

Re: Stacked tensions for chord names

2021-03-01 Thread Robin Bannister
Valentin Petzel wrote: Does anyone of you have an idea how one can set baseline-skip to be proportional to the font-size? Well, when the markup command \fontsize changes the font size, it changes the baseline-skip too, to keep it proportional. But this means that if you are overriding the