Werner LEMBERG writes:
> [2.17.26]
>
> Folks,
>
>
> it seems there isn't an easy possibility to change the size of \tempo
> marks globally. Have I missed something? This code
>
> {
> \tempo "abc" c''1 |
> \override MetronomeMark.font-size = #20
> \override MetronomeMark.font-famil
Werner LEMBERG gnu.org> writes:
> it seems there isn't an easy possibility to change the size of \tempo
> marks globally. Have I missed something?
They are created in the Score context, so
\override Score.MetronomeMark #'font-size = #20
___
lil
> {
> \tempo "abc" c''1 |
> \override Score.MetronomeMark.font-size = #20
> \override Score.MetronomeMark.font-family = #'sans
> \tempo "abc" c''1 |
> }
>
> works just fine.
Oh, how embarassing that I didn't try that. Sorry for the noise.
Werner
__
2013/9/16 David Kastrup :
> [a rant about GitHub being proprietary etc.]
Well, that's true.
I wish github was Free, but see below.
> The whole genesis of Git itself is a story about how "free" proprietary
> services can come to bite you in your behind at the least convenient
> moment: Linux was d
Janek Warchoł writes:
> 2013/9/16 David Kastrup :
>> [a rant about GitHub being proprietary etc.]
>
> Well, that's true.
> I wish github was Free, but see below.
>
>> The whole genesis of Git itself is a story about how "free" proprietary
>> services can come to bite you in your behind at the lea
Hello
I'm having problems with my broadband at home and am not in the office this
week. It means that I cannot run patchy-test or do Countdowns. Patchy-merge
runs from my office machine as well as from home, so that is covered so
depending on how long it takes to fix, you'll have to test patche
James writes:
> Hello
>
> I'm having problems with my broadband at home and am not in the office
> this week. It means that I cannot run patchy-test or do
> Countdowns. Patchy-merge runs from my office machine as well as from
> home, so that is covered so depending on how long it takes to fix,
>
2013/9/17 David Kastrup :
> James writes:
>
>> Hello
>>
>> I'm having problems with my broadband at home and am not in the office
>> this week. It means that I cannot run patchy-test or do
>> Countdowns. Patchy-merge runs from my office machine as well as from
>> home, so that is covered so depend
I'll see whether I can get the full patchy (including docs) running tomorrow or
Thursday.
--
Phil Holmes
- Original Message -
From: James
To: LilyPond-Devel list
Sent: Tuesday, September 17, 2013 12:15 PM
Subject: Patchy test and Countdowns
Hello
I'm having problems
David Kastrup writes:
> This is a reminder that next weekend, Sept 20th to 24th, there will be a
> LilyPond developer and user meeting in Waltrop, Germany.
Ok, the current possible participant list would look like the following:
Jan, Janek, Harm and myself.
Quite a number of people cited a lack
Janek Warchoł writes:
> 2013/9/16 David Kastrup :
>> So the question is what we should be telling the Savannah operators
>> to make working on GNU projects using Git more feasible.
>
> Here you go:
> A web interface with online editor, allowing to create commits from a
> web browser, on any bran
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, September 17, 2013 5:59 PM
Subject: Re: Patchy email
"Phil Holmes" writes:
"/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py",
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee t
"Phil Holmes" writes:
>> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py",
>> line 266, in runner
>>raise FailedCommand ("Failed runner: %s\nSee the log file %s" %
>> (command, this_logfilename))
>> FailedCommand: Failed runner: nice make -j3 CPU_COUNT=3
>> See the lo
16:31:10 (UTC) Begin LilyPond compile, previous commit at
88ce02a0c97434ae1b3903395e5664ce2fbf7e35
16:31:21 Merged staging, now at:88ce02a0c97434ae1b3903395e5664ce2fbf7e35
16:31:22Success:./autogen.sh --noconfigure
16:31:42Success:/tmp/
- Original Message -
From:
To:
Cc:
Sent: Tuesday, September 17, 2013 5:37 PM
Subject: Patchy email
16:31:10 (UTC) Begin LilyPond compile, previous commit at
88ce02a0c97434ae1b3903395e5664ce2fbf7e35
16:31:21 Merged staging, now at: 88ce02a0c97434ae1b3903395e5664ce2fbf7e35
16:31:22 S
Am 17.09.2013 18:21, schrieb David Kastrup:
Janek Warchoł writes:
2013/9/16 David Kastrup:
So the question is what we should be telling the Savannah operators
to make working on GNU projects using Git more feasible.
Here you go:
A web interface with online editor, allowing to create commits
Urs Liska writes:
> You are doing code reviews through a web interface already, isn't it?
> And this is because that's a quite natural way to communicate, comment
> on code etc. You can't do _that_ with plain Git.
To me, this is one the most unnatural and therefore annoying parts of
current devel
17 matches
Mail list logo