Variables, tags, filtering, conditions

2024-05-19 Thread Giles Boardman
Hello, I am an occasional Bb clarinetist and very bad at transposing on the fly. I would like to create alternative versions of a score based on the value of a parameter. I have been using variables to hold phrases and sections, but I can't find how to test their contents. I have read about con

Re: Variables, tags, filtering, conditions

2024-05-19 Thread Timothy Lanfear
On 19/05/2024 11:36, Giles Boardman wrote: Hello, I am an occasional Bb clarinetist and very bad at transposing on the fly. I would like to create alternative versions of a score based on the value of a parameter. How about this as a solution? \version "2.24.0" instrument = "clarinet" tp

Re: Variables, tags, filtering, conditions

2024-05-19 Thread Giles Boardman
Hello Timothy, Looks about perfect to me. Thank you very much. I can see how it's working and there are obviously a lot of other programming possibilities hinted at that I haven't found the documentation for. Where do I read about #( if (string=? and (set! ? Thanks Giles ___

Re: Disable all padding and collision around markup

2024-05-19 Thread kieren
Hi William, In the following example, I use a section label and a TextScript on a note. I offset the markup text so that it appears inside the staff, but it still makes the section text higher up. I would like to know if it is possible to disable this padding around the TextScript, so that the

Re: Variables, tags, filtering, conditions

2024-05-19 Thread Timothy Lanfear
On 19/05/2024 12:11, Giles Boardman wrote: Hello Timothy, Looks about perfect to me. Thank you very much. I can see how it's working and there are obviously a lot of other programming possibilities hinted at that I haven't found the documentation for. Where do I read about #( if (string=? an

Re: Disable all padding and collision around markup

2024-05-19 Thread Knute Snortum
On Sun, May 19, 2024 at 4:22 AM wrote: > Hi William, > > > In the following example, I use a section label and a TextScript on a > > note. I offset the markup text so that it appears inside the staff, but > > it still makes the section text higher up. I would like to know if it > > is possible to

Re: Disable all padding and collision around markup

2024-05-19 Thread Kieren MacMillan
Hi Knute, >> There are ways to "disable the padding" (a.k.a. have the spacing engine >> ignore the TextScript). However, it might be just as easy — or maybe >> even easier? — to simply tweak the X-offset and Y-offset rather than >> using extra-offset: > The extra-offset happens late in the rend

Looking for documentation for constants

2024-05-19 Thread Ken Ledeen
Hello, This is a very basic question. I have see some examples that use constants like "$SELECTION" or ""$CURSOR'$ANCHOR". but despite doing all the obvious things (searching the documentation, etc.) I've not found any relevant information. I would sincerely appreciate being pointed in the right

Re: Looking for documentation for constants

2024-05-19 Thread Jean Abou Samra
> This is a very basic question.  I have see some examples that use > constants like "$SELECTION" or ""$CURSOR'$ANCHOR". but despite doing all the > obvious things (searching the documentation, etc.) I've not found any relevant > information. > > I would sincerely appreciate being pointed in the r

Re: Disable all padding and collision around markup

2024-05-19 Thread William Rehwinkel via LilyPond user discussion
This is perfect, thanks so much for your responses everybody. -William On 5/19/24 10:56, Kieren MacMillan wrote: Hi Knute, There are ways to "disable the padding" (a.k.a. have the spacing engine ignore the TextScript). However, it might be just as easy — or maybe even easier? — to simply twea

Conditional code in the midi block

2024-05-19 Thread Carolyn Beeton
I would like to include some Staff and Voice context settings in the \midi block only if a flag is set to ##t and I have not been able to figure out how to do this. When I try to wrap the \context blocks in a code block with #{…#} I get this error: trackPerVoiceMWE.ly:31:16: error: syntax error