dear Paolo,
rhanks, that helped me a lot. There is one more thing: how çan I set the
default include path for lilypond?
Paolo Prete schrieb am Fr., 31. Mai 2024, 21:18:
> Check here (tell me if you have issues):
>
>
> https://github.com/paopre/Spontini/blob/master/documentation/miscellaneous.md#
Hi Stefan, do you mean the following flag?:
-I, --include=directory
This Is not currently supported. But given that it's a trivial addition, I
can add It to the editor, along with other options, right now.
Please let me know
Il sab 1 giu 2024, 10:23 Stefan Thomas ha
scritto:
> dear Paolo,
> r
Hi Federico,
I’ve adjusted my snippet a little, and I think it might handle all your spacing
issues…? Let me know!
Best,
Kieren.
%%% SNIPPET BEGINS
\version "2.25.15"
\paper {
system-system-spacing.padding = 4
}
\layout {
\context {
\type "Engraver_group"
\name TS
keepAliveIn
Hi!
I am running on Alpine Linux and I noticed that lilypond creates
~/.fontconfig/ with cache files every time I run it.
It seems like fontconfig is supposed to follow the XDG environment
variables
(https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/8c255fb),
which I have defined on
> I am running on Alpine Linux and I noticed that lilypond creates
> ~/.fontconfig/ with cache files every time I run it.
>
> It seems like fontconfig is supposed to follow the XDG environment
> variables
> (https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/8c255fb),
> which I have def
I just added the feature on a new release. Please download:
https://github.com/paopre/Spontini/releases/tag/1.24_alfa
and read here:
https://github.com/paopre/Spontini/blob/master/documentation/miscellaneous.md#additional-compile-optionsflags
Please tell me if it's all OK!
Hope this helps
Chee
Hi Kieren,
Thanks for your answer and time. It looks really nice!
However, it seems that both solutions run along similar lines: redefining
contexts. In your solution you split the topmost layout objects from the
staff context in two different contexts and create another -the bottom
one-. In my
Hi Federico,
> However, it seems that both solutions run along similar lines: redefining
> contexts. In your solution you split the topmost layout objects from the
> staff context in two different contexts and create another -the bottom one-.
> In my solution, I redefine the staff context to a
Hello kind community folk,
how do I make \wordwrap act correctly on the argument to this markup
function?
And why does \line not make \box act on the markup as a whole, as it is
said to do?
Best, Simon
\version "2.25.14"
#(define-markup-command (freely layout props width-param text) (numb
> (define-markup-command (freely layout props width-param text) (number?
> markup?)
^^^
Make that `markup-list?`. Otherwise, your command is accepting only
a single markup. In your example, \line inside the command is
10 matches
Mail list logo