On 16/03/2026 09:07, Luca Fascione wrote:
unless your \parallelMusicExtended function
took a string as its second argument and preprocessed that string
before
handing it to the LilyPond parser as LilyPond syntax (using one of
the
ly:parser… scheme functions, been ages since I used them).
Yes, that's what I meant indeed
But then thislong string would be extremely unwieldy as input, so
I can’t imagine
that being worth it.
I don't follow, why isn't it identical to what parallelMusic takes today?
What am I missing here?
Again, I didn’t try to implement or test this, but as far as I know you
could only make this a music function if the input looked like this:
%%%%%%%%%
\parallelMusicExtended #'((chordmode . chords) voiceA (lyricmode .
lyricsOne) (lyricmode . lyricsTwo)) "{
c2. |
c2 e8 c |
ma -- zing __ _ |
grace that __ _ |
}"
%%%%%%%
And I would find having the whole music expression inside "", without
syntax highlighting, auto-formatting or point-and-click, prohibitively
unwieldy.
Best, Simon
