I tried it with %%% \line {\fromproperty #'header:composer " - " \as-string \fromproperty #'header:title } %%% - then the title (in the footnote) was empty. But you gave so many valuable insigh
Hi Aaron, thx for your input - I'm aware of separating those information in include files, just tried to make a minimal example :) And I aim to separate content from style - but in order to have the
I'd like to make an automatic footer, using infos from the header block. What do I have to change, to get rid of (or override) the format from the title? --8<-- \version "2.24.0" {a4} \header { ti
There's may be one extra paren in there because it threw a syntax error. Yes, sorry. Is that a proper fix, or is something else wrong? I wouldn't call it a “proper” fix because it's a bit too dep
There's may be one extra paren in there because it threw a syntax error. I removed one paren and it seems to work: germanNoteNames = (let* ((default-name (markup->string (ly:grob-property grob 'text)
This code is too big for me to digest it, but the basic problem is that (let* ((default-name (ly:grob-property grob 'text)) (new-name (assoc-get default-name newnames))) is doing a lookup in your n
Le 06.08.23 à 16:59, David Kastrup a écrit : Strange... I tried a few things, but did not find a way to make it work. I noticed 2 things : 1. In this association table : chimenames = ("c"
Le dimanche 06 août 2023 à 18:36 +0200, Robin Bannister a écrit : David Kastrup wrote: Note names have changed to use ♯ and ♭ characters, so you need to look up "c♯" instead of "cis". I got
Strange... I tried a few things, but did not find a way to make it work. I noticed 2 things : 1. In this association table : chimenames = ("c" . "C") ("cis" . "C♯") ("d" . "D
Hello, I have been using the syntax below for several years; the last code update I did was in December 2022, and it worked well since. Today I noticed that I can't get the sharp/flat note names pr
Le vendredi 16 juin 2023 à 09:41 -0400, Kieren MacMillan a écrit : Hi all! Anyone have a good \uppercase function they could share? I tried to make one, and it doesn’t throw an error, but also d
Hi all! Anyone have a good \uppercase function they could share? I tried to make one, and it doesn’t throw an error, but also doesn’t work: \version "2.25.2" (interpret-markup layout props (strin
[...] Well, one reason to avoid deprecated syntax and use convert-ly for updates is that it avoids masking the real problem when people like myself stop looking further after seeing the presumed firs
Viktor, I suspect what is happening is that you first upgraded an old file to 2.20 without convert-ly, which didn't change this syntax, then upgraded from 2.20 to 2.22, which didn't change it either
Le 11/11/2022 à 14:28, David Kastrup a écrit : \override NoteName #'stencil = #ChimeNoteNames This is the problematic line, and the error message should have indicated as much. This should be Note
Whoops, yes. Not sure how I didn't see that they weren't sorted. Maybe I did a test and sent the wrong version? Weird. Anyway, thanks for the correction.
Le 21/09/2022 à 20:39, Valentin Petzel a écrit : Hello Jean, at least for me this code fails to change the order of the toc. The reason for this is that toc-markup does not in fact contain the mar