Jean Abou Samra knew how to fix that behaviour of arpeggios, so here's
a (I hope) working solution:
It seems we can continue this game of "LilyPond experts explain how to
do things and I only have to post the resulting, ever simpler examples"
for some time. :-)
Harm pointed out in
https:
Hi all,
I'm trying to set the default Lilypond behaviour *not* to print natural
signs before restored accidentals, but I can't figure out the proper
syntax. Can someone tell me why the \override line in the following example
doesn't work but the \tweak does, and what I need to do to apply this
beh
Hi all,
> It seems we can continue this game of "LilyPond experts explain how to do
> things and I only have to post the resulting, ever simpler examples" for some
> time. :-)
Ha! Looking forward to the inevitable “one-line-of-code” version. ;)
> Harm pointed out in
> https://gitlab.com/lilyp
Brent Annable writes:
> Hi all,
>
> I'm trying to set the default Lilypond behaviour *not* to print natural
> signs before restored accidentals, but I can't figure out the proper
> syntax. Can someone tell me why the \override line in the following example
> doesn't work but the \tweak does, and
Lukas-Fabian Moser writes:
>> Jean Abou Samra knew how to fix that behaviour of arpeggios, so
>> here's a (I hope) working solution:
>
> It seems we can continue this game of "LilyPond experts explain how to
> do things and I only have to post the resulting, ever simpler
> examples" for some time
David,
Many thanks!
Brent.
On Wed, 13 Oct 2021 at 00:24, David Kastrup wrote:
> Brent Annable writes:
>
> > Hi all,
> >
> > I'm trying to set the default Lilypond behaviour *not* to print natural
> > signs before restored accidentals, but I can't figure out the proper
> > syntax. Can someone
I'm writing an orchestra piece with a lot of time signature changes. I was
wondering if there is a way to put all the time signature changes into one
place, and use that in all parts? For example, if I want to later change a 6/4
to 3/2, I would only need to change it in one place and not for all
set! is very unidiomatic Scheme. You could use
(let* ((one (begin (ly:grob-set-property! ...) (ly:arpeggio::print grob)))
((two ...
Yes, I'm aware that set! isn't really the essence of what functional
programming languages are meant for. But basically the whole idea of
"putting the
Hi Erika!
This is pretty easily accomplished. Just put the time signature changes in
a seperate variable, eg.:
changes = {
\time 4/4
s1*15
\time 3/4
s2.*14
\time 2/4
s2*10
}
trombone = \relative {
%notes
}
\new Staff {
<<
\changes
\trombone
>>
You can also put rehearsal marks and special bar l
Lukas-Fabian Moser writes:
>> set! is very unidiomatic Scheme. You could use
>> (let* ((one (begin (ly:grob-set-property! ...) (ly:arpeggio::print grob)))
>>((two ...
>
> Yes, I'm aware that set! isn't really the essence of what functional
> programming languages are meant for. But basic
From: lilypond-user
on behalf of Erika Pirnes
Date: Tuesday, October 12, 2021 at 8:09 AM
To: "lilypond-user@gnu.org"
Subject: Time signatures for all parts
I'm writing an orchestra piece with a lot of time signature changes. I was
wondering if there is a way to put all the time signature ch
No. "in some unspecified order":
R5RS:
Ah, thanks! I only had the Guile documentation, which is not quite as
explicit in that respect. (Ok, they mention for let* that _here_ the
assignments are done from left to right, but ...).
Lukas
Lukas-Fabian Moser writes:
>> No. "in some unspecified order":
>>
>> R5RS:
>
> Ah, thanks! I only had the Guile documentation, which is not quite as
> explicit in that respect. (Ok, they mention for let* that _here_ the
> assignments are done from left to right, but ...).
Strictly speaking "in
Le 12/10/2021 à 15:33, David Kastrup a écrit :
but I don't even know whether there is a guarantee that
ly:arpeggio::print is happy with the grob being modified after the call
and before the stencil is getting used. Looking at the C++ code, that
appears to be the case. Maybe giving ly:arpeggio::
Le 09/10/2021 à 21:47, David F. a écrit :
I did notice that the \markup defeats lyric ties.
You can special-case bare strings to return a string:
\version "2.22.1"
openQuote =
#(define-scheme-function (text) (markup?)
(if (string? text)
(string-append "“" text)
#{ \markup \co
15 matches
Mail list logo
