Hello and thank you very much for your input on this topic. I will try to
follow the suggestions and implement my own procedure for the note names.
I'll report back if I have success or new questions.
Again, thank you very much!
> 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 dependent on details
that can easily change (specifically, whether the default `NoteName` text is
On Wed, 2023-12-13 at 21:29 +0100, Jean Abou Samra wrote:
> The quick fix here is to change
>
> (let* ((default-name (ly:grob-property grob 'text)))
> to
>
> (let* ((default-name (markup->string (ly:grob-property grob 'text
>
> in order to first get an approximate string representation of
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 `newnames` alist with the value of `text` as the key.
In more recent
Stefano Antonelli wrote:
A good place to start is a minimum working example. I can't help debug
this, but I put together a minimum working example that shows the
problem. Maybe someone with better scheme can spot the problem.
With liilypond v2.20 there is no issue. With lilypond v2.23.3
On Wed, 2023-12-13 at 11:12 +0100, Sebastian Käppler wrote:
> Any help on this would be appreciated, I'm a bit lost now where to
> start.
A good place to start is a minimum working example. I can't help debug
this, but I put together a minimum working example that shows the
problem. Maybe
Dear lilypond experts,
I seem to have missed some changes to LilyPond between 2.19.82 and current
versions. I use a quite big script to automatically generate some music
theory tasks for my students (in German). I'll post the complete example
below. However, my code for creating note names
