Am Sa., 10. Apr. 2021 um 22:26 Uhr schrieb Jean Abou Samra :
>
> Le 10/04/2021 à 19:16, Thomas Morley a écrit :
>
> > Am Sa., 10. Apr. 2021 um 17:55 Uhr schrieb Thomas Morley
> > :
> >> I'll check for your recent changes soon.
> > Apart from a nit (below) all looks great now.
> >
> > You did not
Le 10/04/2021 à 19:16, Thomas Morley a écrit :
Am Sa., 10. Apr. 2021 um 17:55 Uhr schrieb Thomas Morley
:
I'll check for your recent changes soon.
Apart from a nit (below) all looks great now.
You did not extend section "Introduction to extending - Printing
values" with other printing
On Sat, 10 Apr 2021 at 20:13, N Trocado wrote:
>
> What's wrong with the snippet bellow? It doesn't print the cue notes,
unless I remove \fluteA and \oboeA.
Hello,
It is not 100% clear to me but it seems LilyPond is trying to quote the
second measure of oboeB, which is empty.
This works:
What's wrong with the snippet bellow? It doesn't print the cue notes, unless I
remove \fluteA and \oboeA.
\version "2.19.55"
fluteA = {
r1
}
oboeA = {
r1
}
fluteB = {
\cueDuring #"oboeB" #DOWN { R1 }
}
oboeB = {
c4 c c c
}
\addQuote "oboeB" { \oboeB }
\score{
<<
\new Staff {
Am Sa., 10. Apr. 2021 um 17:55 Uhr schrieb Thomas Morley
:
> I'll check for your recent changes soon.
Apart from a nit (below) all looks great now.
You did not extend section "Introduction to extending - Printing
values" with other printing procedures.
Mentioned are `display' and `write' from
Am Sa., 10. Apr. 2021 um 16:47 Uhr schrieb Jean Abou Samra :
> Just a question: you say
>
>In music-functions, when calling a variable
>containing music .$ is preferable, because
>otherwise a subsequent call of the same
>variable will not see the original.
>
> Is that not due to
Hi Jean,
First of all, thank you so much for this resource — I am the perfect target
audience, and I can’t wait to dive into it.
> I was absolutely astounded by this!
> \markup foo = \markup \with-color #red \etc
> \markup \foo "arg"
I find \etc astounding.
It’s one of the main examples I give
Hi Harm,
Le 10/04/2021 à 15:43, Thomas Morley a écrit :
Am Sa., 10. Apr. 2021 um 13:10 Uhr schrieb Thomas Morley
:
Hi Jean,
this is great work. I'd wish it would have been available years ago.
at the time I undertook exploring said "thorny path".
Well, I have to say that I could never have
Dear Jonas,
thanks for Your reply.
I send You the complete fille:
> \version "2.22.0"
> \include"arranger.ly"
> global = { s1*1000 }
> %% a long length is provided
> #(init '())
> %% Instruments list initially empty =>
> %% the positions take into account previous timing insertions.
> %% (
Am Sa., 10. Apr. 2021 um 13:10 Uhr schrieb Thomas Morley
:
>
> Am Mo., 5. Apr. 2021 um 21:38 Uhr schrieb Jean Abou Samra
> :
> >
> > Hi,
> >
> > A frequent complaint on this list is the lack
> > of available documentation about LilyPond's
> > inner workings and programming interfaces.
> >
> >
Am Mo., 5. Apr. 2021 um 21:38 Uhr schrieb Jean Abou Samra :
>
> Hi,
>
> A frequent complaint on this list is the lack
> of available documentation about LilyPond's
> inner workings and programming interfaces.
>
> Indeed, I have myself experienced the thorny
> path to getting a grasp of how to
Hi Stefan,
it's of course possible that arranger.ly is not yet prepared for
LilyPond 2.22.0. In any case, it might help to post the exact error
message (if there is one other than "GUILE signaled an error") so
others can try to help.
Jonas
Am Samstag, dem 10.04.2021 um 12:28 +0200 schrieb
Dear community,
I've remove lyp and I've also uninstalled and reinstalled lilypond but the
problem still persists.
Does someone of You know, what I could do now?
Thanks,
Stefan
Am Fr., 9. Apr. 2021 um 17:20 Uhr schrieb Stefan Thomas <
kontrapunktste...@gmail.com>:
> Dear Jonas,
> I've download
Le 10/04/2021 à 10:34, Kevin Barry a écrit :
On Sat, Apr 10, 2021 at 10:09:01AM +0200, Jean Abou Samra wrote:
By the way, it looks like this issue is not present in 2.20...?
Sorry, I'm not following, what issue exactly?
Harm's original issue with incorrect skylines. I ran his code through
On Sat, Apr 10, 2021 at 10:09:01AM +0200, Jean Abou Samra wrote:
> > By the way, it looks like this issue is not present in 2.20...?
>
> Sorry, I'm not following, what issue exactly?
Harm's original issue with incorrect skylines. I ran his code through
2.20 and the skylines were fine. Something
Le 09/04/2021 à 19:29, Kevin Barry a écrit :
By the way, it looks like this issue is not present in 2.20...?
If someone already said that then I apologise for missing it. I wonder
if we should be looking for the commit that changed it.
Sorry, I'm not following, what issue exactly?
Other
16 matches
Mail list logo
