[Berhard]
Actually, the lilypond.org web server was very insistent that even
when I googled English, I should read German whenever it was
available; therefore I assumed the versions were on par. I will think
about configuring one browser / profile without language preferences
so that I can
Good morning, Jean,
thank you very much for your detailed explanation! This helps me to
understands things a bit better.
Jean Abou Samra schrieb am 21.01.22 um 19:30:
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
- There is a point in processing when one has to convert every
Hi Lukas,
Lukas-Fabian Moser schrieb am 21.01.22 um 17:15:
Also note
[...]
The standard use case for make-XXX-markup is explained in:
http://lilypond.org/doc/v2.23/Documentation/extending/markup-construction-in-scheme.html
under "Known issues and warnings".
I had read that, and it seemed
Jean Abou Samra writes:
> Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
>> Good morning,
>>
>> Consequence: There is no collision between an auxiliary function
>> CMD and a homonymous markup command \CMD, as they are (CMD ...) and
>> (make-CMD-markup ...), respectively, in scheme.
>
>
>
plans of similar scope, and [I] work on LilyPond as a
hobby in otherwise already LilyPond development
is for me a hobby in already otherwise busy weeks.
Talk about busy weeks...
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
Good morning,
trying to understand the programming a bit better, I managed to
transform the mixed command definitions to scheme code (see below).
I've learnt the following in the process; should some of it be made
more explicit in the
Also note that your function, if called with \strut-line { hello world
}, actually adds your invisible strut to every word of the line. (Just
remove the make-transparent-markup in your function to see this, or,
more easuily, remove the #:transparent in my version). Compare:
\markup
Hi Bernhard,
unfortunately I don't have much time at the moment (and there's always
the chance that Jean or someone else more knowledgeable than me is
already working on an exhaustive answer), but there's one thing I'd like
to point out:
#(define-markup-command (strut-line layout props
Good morning,
trying to understand the programming a bit better, I managed to
transform the mixed command definitions to scheme code (see below).
I've learnt the following in the process; should some of it be made more
explicit in the manual? (If so, I could try to think of suggestions.)
