So I have my Ubuntu VM setup and per the link from Jean, I've ran autogen,
but when I try to do "../configure --enable-cairo-backend", it says
"configure: error: no acceptable C compiler found in $PATH". How should I
fix this?
On Mon, Jul 18, 2022 at 2:57 PM Silvain Dupertuis <
silvain-dupert...@b
Great, glad you could get it working Kenneth. Speaking for myself, I
found it easiest to think of \repeat tremolo in the same way as the
other \repeat commands... the first number is how many times the note
repeats.
-William
On 7/18/22 20:44, Kenneth Wolcott wrote:
Hi William;
Thank you!
Hi William;
Thank you! That is exactly what I needed. I still don't have the
formula down pat, but I'll work on it until it is automatically
correct.
Ken
On Mon, Jul 18, 2022 at 5:40 PM William Rehwinkel
wrote:
>
> Hey Kenneth,
>
> I think you may want to write `\repeat tremolo 4` instead of
Hey Kenneth,
I think you may want to write `\repeat tremolo 4` instead of 2, because
that will signify four repeating eighth notes, which will result in the
time of a half note...unless i am misunderstanding.
Thanks,
-William
On 7/18/22 20:34, Kenneth Wolcott wrote:
Hi;
I was able to g
Hi;
I was able to generate two half-note, single-slashed tremolos in 4/4
time using the colon syntax, but do not understand how to get the same
effect with the repeat tremolo syntax:
\repeat tremolo 2 8 \repeat tremolo 2 8 | % m01
2:8 q:8 | % m02
bar #2 is
It'll be interesting to be able to ouput SVG directly to get snippet which can be
integrated into other documents.
Actually, one can get SVG files using Inkscape : import the PDF file (using PopplerCairo
orption), edit at will, select parts, crop, etc. and save as SVG.
This is what I did for
My gosh it's that simple. I feel laughably stupid right now.
On Mon, Jul 18, 2022 at 1:33 PM David Wright
wrote:
> On Mon 18 Jul 2022 at 11:28:26 (-0500), DoubleFelix wrote:
> >
> > > Felix, I’m curious what you mean by cropping the file. Sounds to me
> like
> > > you are trying to just write a
Thanks for this, David. As unfortunately my method (set \header{tagline=##f}
and run lilypond -dbackend=eps —png file.ly) doesn’t work for SVGs.
-William
Sent from my iPhone
> On Jul 18, 2022, at 14:36, David Wright wrote:
>
> On Mon 18 Jul 2022 at 11:28:26 (-0500), DoubleFelix wrote:
>>
>
On Mon 18 Jul 2022 at 11:28:26 (-0500), DoubleFelix wrote:
>
> > Felix, I’m curious what you mean by cropping the file. Sounds to me like
> > you are trying to just write a small snippet of music, maybe a few
> > measures, and not have the output flooded by whitespace all around the size
> > of an
Thomas Morley writes:
> I will not vanish from the list/project in the foreseeable future,
> unless hit by bus...
>
> Though in my humble opinion meaningful error messages are the most
> pressing issue and I don't see I could do anything to improve the
> situation.
> That is frustrating, furtherm
Am Mo., 18. Juli 2022 um 18:43 Uhr schrieb Lukas-Fabian Moser :
>
> Forgive me for piping up:
> > I'm not able to say what happened, I'm not able to debug because of
> > that unhelpful (oh, I'm very polite this evening) guile messages, see
> > the other thread.
> >
> > I'm overtired like hell, clos
Forgive me for piping up:
I'm not able to say what happened, I'm not able to debug because of
that unhelpful (oh, I'm very polite this evening) guile messages, see
the other thread.
I'm overtired like hell, close to trashing the whole project, and
close to advertising everyone to not use LilyPon
To William:
> Felix, I’m curious what you mean by cropping the file. Sounds to me like
> you are trying to just write a small snippet of music, maybe a few
> measures, and not have the output flooded by whitespace all around the size
> of an A4 paper? This is also similar to what I was using lilyp
Hi William, hi Jim,
Le lun. 18 juil. 2022 à 16:38, William Rehwinkel <
will...@williamrehwinkel.net> a écrit :
> Hey Jim,
>
> To be honest, I'm not sure why the example you posted doesn't work, but I
> was able to find a workaround by using \contexts to apply the override to
> each staff, like so
Hi William, hi Jim,
Le lun. 18 juil. 2022 à 16:38, William Rehwinkel <
will...@williamrehwinkel.net> a écrit :
> Hey Jim,
>
> To be honest, I'm not sure why the example you posted doesn't work, but I
> was able to find a workaround by using \contexts to apply the override to
> each staff, like s
Hey Jim,
To be honest, I'm not sure why the example you posted doesn't work, but
I was able to find a workaround by using \contexts to apply the override
to each staff, like so.
\version "2.20.0"
upper = \relative c'' { % remove \override
\clef treble
\key c \major
\time 4/4
a-1 cis'
> lower = \relative c {
>\override Fingering.color = #red
This line could be changed to read
>\override Staff.Fingering.color = #red
which “speaks” to the right context.
You could also replace the two \override with something like this:
> \score {
>\new PianoStaff <<
> \set Pi
Hi David, thanks, I have attached a 1-measure example that illustrates the
problem. The upper staff is showing the requested color for the
fingering. I can see now that it has to do with the <<{}\\{}>> construct.
The override does not apply to objects within << >> apparently. Any
suggestions
Jim Cline writes:
> I want to change the fingering color to red in my piano score.
> Using
>
> upper = \relative c'' {
>\override Fingering.color = #red
>
> for the upper staff works, but adding the same for the lower staff
>
> lower = \relative c {
> \override Fingering.color = #red
>
> le
I want to change the fingering color to red in my piano score.
Using
upper = \relative c'' {
\override Fingering.color = #red
for the upper staff works, but adding the same for the lower staff
lower = \relative c {
\override Fingering.color = #red
leaves the fingering in black in the lowe
Am Mo., 18. Juli 2022 um 11:16 Uhr schrieb Jean Abou Samra :
>
> Le 17/07/2022 à 17:03, David Sumbler a écrit :
> > At the moment I am testing it on a short file - in fact, your
> > "grow-in-up-direction" example from the Extending Lilypond document.
> > Compiling it is taking over 80 seconds each
Am Mo., 18. Juli 2022 um 11:02 Uhr schrieb Jean Abou Samra :
>
> Le 17/07/2022 à 23:33, Thomas Morley a écrit :
> > Sorry for the delayed reply!
> > I now tried to make some steps for scm-files/ly:load/autocompile.
> >
> > Though, as far as I can tell ly:load doesn't work with relative pathes.
>
>
Jean Abou Samra writes:
> Le 18/07/2022 à 00:59, David Kastrup a écrit :
>> Harm is not a C programmer either. Scheme is his only language and he
>> learnt it because of LilyPond. So he has no exposure to the low-level
>> nature of C++, nor to the basics of imperative programming languages
>> t
Le 17/07/2022 à 17:03, David Sumbler a écrit :
At the moment I am testing it on a short file - in fact, your
"grow-in-up-direction" example from the Extending Lilypond document.
Compiling it is taking over 80 seconds each time; after the first
time, I would expect a file like this to take only
Le 17/07/2022 à 23:33, Thomas Morley a écrit :
Sorry for the delayed reply!
I now tried to make some steps for scm-files/ly:load/autocompile.
Though, as far as I can tell ly:load doesn't work with relative pathes.
As said on the issue, I misremembered what ly:load does, sorry.
Use add-to-load
Le 18/07/2022 à 00:59, David Kastrup a écrit :
Harm is not a C programmer either. Scheme is his only language and he
learnt it because of LilyPond. So he has no exposure to the low-level
nature of C++, nor to the basics of imperative programming languages
that are sort of a required firm footin
26 matches
Mail list logo
