Hi Nicolas,
many thanks for that hint!
Using make-score was the point. But also very nice you showed me how to
deal with layout settings in such a "scheme score".
Michael
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mail
Le 23 févr. 09 à 10:36, Michael Käppler a écrit :
Hi,
I don't know if it will work, but perhaps you can try to type
\displayMusic {<< \clef #testclef a4 h c >>} to get the scheme
version of your music,
and to copy/paste the output you got after the #:score markup ...
good idea! But it stil
Hi,
I don't know if it will work, but perhaps you can try to type
\displayMusic {<< \clef #testclef a4 h c >>} to get the scheme
version of your music,
and to copy/paste the output you got after the #:score markup ...
good idea! But it still doesn't work. Let's look at the following
minimal
3 +0100
> Von: "Michael Käppler"
> An: lilypond-user@gnu.org
> Betreff: \\score inside define-markup-command
> Hi all,
> is it possible to use the \score markup function in a new defined markup
> function construct?
>
> For example,
>
> #(define-markup
#(define-markup-command (test layout props testclef) (string?)
(interpret-markup layout props (markup #:score ( << \clef #testclef a4 h
c >>
This is invalid code because it mixes LilyPond and Scheme syntax. How can
I achieve something similar to what's expressed in this dummy code pie
Hi all,
is it possible to use the \score markup function in a new defined markup
function construct?
For example,
#(define-markup-command (test layout props testclef) (string?)
(interpret-markup layout props (markup #:score ( << \clef #testclef
a4 h c >>
This is invalid code because
