09:24:04 (UTC) Begin LilyPond compile, previous commit at
309687117b7a10b20cd958147174a906e308ccb6
09:24:16 Merged staging, now at:309687117b7a10b20cd958147174a906e308ccb6
09:24:18Success:./autogen.sh --noconfigure
09:24:43Success:/tmp/
pat...@gnu.org writes:
> 09:24:04 (UTC) Begin LilyPond compile, previous commit at
> 309687117b7a10b20cd958147174a906e308ccb6
> 09:24:16 Merged staging, now at: 309687117b7a10b20cd958147174a906e308ccb6
> 09:24:18 Success:./autogen.sh --noconfigure
> 09:24:43 Suc
A bit late, but here it is:
- a lot of work is being done on correct rendering of Stems and other
objects in pdf output. This was a longstanding issue, but i think
there's a fair chance of the fix being available in 2.18:
http://code.google.com/p/lilypond/issues/detail?id=2658
https://codereview.
Eluze wrote
>
> ArnoldTheresius wrote
>>
>> Eluze wrote
>>> ...
>>> maybe my hope to find the needed information in thess tables was to
>>> optimistic - does somebody know how the "correct" way is?
>>>
>>> Eluze
>> Well, at least here is what I did try this weekend - posted before I read
>> all
Hello.
On 23 April 2013 11:18, David Kastrup wrote:
> pat...@gnu.org writes:
>
> > 09:24:04 (UTC) Begin LilyPond compile, previous commit at
> 309687117b7a10b20cd958147174a906e308ccb6
> > 09:24:16 Merged staging, now at:
> 309687117b7a10b20cd958147174a906e308ccb6
> > 09:24:18 Success:
ArnoldTheresius writes:
> Eluze wrote
>>
>>> - Which one needs to be started into the background (like lilypad)?
>> what do you mean exactly? (I can start: lilypad "d:\data\ly\test\test.ly"
>>
>> after finding a viable way textedit and it's prerequisites should be
>> documented clearer (in AU).
hmm. i don't see any protests so i'll push it.
2013/4/21 Janek Warchoł :
> 2013/4/21 David Kastrup :
>> Janek Warchoł writes:
>>
>>> http://code.google.com/p/lilypond/issues/detail?id=3309
>>> https://codereview.appspot.com/8614045
>>>
>>> This had passed countdown (with 0 reviews). I'm not sure
anyway, this patch LTGM.
https://codereview.appspot.com/8647044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
generally LGTM.
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely
File Documentation/extending/programming-interface.itely (right):
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely#newcode413
Docume
LGTM
https://codereview.appspot.com/8538050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
https://codereview.appspot.com/8853044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
https://codereview.appspot.com/8758047/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely
File Documentation/extending/programming-interface.itely (right):
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely#newcode413
Documentation/extending
LGTM
https://codereview.appspot.com/8540046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, April 23, 2013 1:08 PM
Subject: Re: Point and Click does not work on Windows
ArnoldTheresius writes:
Who will (and can off course) initiate the modification to the
installer and the lilypond-invoke-editor script?
The l
ooops, seems like i'd fallen behind. The last thing i remembered
about \tweak syntax was this:
http://code.google.com/p/lilypond/issues/detail?id=2540
Back then the syntax was
\tweak optional-grobname property value music
And i liked it. Somehow i didn't realize that this was changed into
\tweak
Janek Warchoł writes:
> ooops, seems like i'd fallen behind. The last thing i remembered
> about \tweak syntax was this:
> http://code.google.com/p/lilypond/issues/detail?id=2540
> Back then the syntax was
> \tweak optional-grobname property value music
> And i liked it. Somehow i didn't realiz
Hi,
2013/4/23 David Kastrup :
> Janek Warchoł writes:
>> Btw, issue 2540 made it possible to write
>>
>> \version "2.17.3"
>> { < \tweak Accidental #'color #red cis' fis'' > }
>>
>> which colored the sharp of the cis. Is it possible to achieve the
>> same goal with newer versions? I've tried so
Janek Warchoł writes:
> Hi,
>
> 2013/4/23 David Kastrup :
>> Janek Warchoł writes:
>>> Btw, issue 2540 made it possible to write
>>>
>>> \version "2.17.3"
>>> { < \tweak Accidental #'color #red cis' fis'' > }
>>>
>>> which colored the sharp of the cis. Is it possible to achieve the
>>> same goa
2013/4/23 David Kastrup :
> Janek Warchoł writes:
>
>> Hi,
>>
>> 2013/4/23 David Kastrup :
>>> Janek Warchoł writes:
Btw, issue 2540 made it possible to write
\version "2.17.3"
{ < \tweak Accidental #'color #red cis' fis'' > }
which colored the sharp of the cis. Is
Janek Warchoł writes:
> 2013/4/23 David Kastrup :
>> Janek Warchoł writes:
>>
>>> Hi,
>>>
>>> 2013/4/23 David Kastrup :
Janek Warchoł writes:
> Btw, issue 2540 made it possible to write
>
> \version "2.17.3"
> { < \tweak Accidental #'color #red cis' fis'' > }
>
> wh
2013/4/23 David Kastrup :
> Janek Warchoł writes:
>> So, a \tweak gets, so to speak, "internally transformed to an
>> override"? This is cool!!
>
> Well, it no longer has music to apply to, only a grob name. I am not
> enthused about the resulting syntax/order when one _does_ need to
> specify p
Janek Warchoł writes:
> 2013/4/23 David Kastrup :
>> Janek Warchoł writes:
>>> So, a \tweak gets, so to speak, "internally transformed to an
>>> override"? This is cool!!
>>
>> Well, it no longer has music to apply to, only a grob name. I am not
>> enthused about the resulting syntax/order whe
2013/4/23 David Kastrup :
> Janek Warchoł writes:
>
>> 2013/4/23 David Kastrup :
>>> Janek Warchoł writes:
So, a \tweak gets, so to speak, "internally transformed to an
override"? This is cool!!
>>>
>>> Well, it no longer has music to apply to, only a grob name. I am not
>>> enthused
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely
File Documentation/extending/programming-interface.itely (right):
https://codereview.appspot.com/8859044/diff/1/Documentation/extending/programming-interface.itely#newcode413
Documentation/extending
Hello,
I'll be able to squeeze in one more countdown in 2 instead of 3 days which
I'll do.
This might not be enough for everyone to review, so I'll hope those devs
involved will make allowances for that.
There's a mix of doc and complex (seemingly) patches that are going to be
easy/difficult to
On 2013/04/23 13:14:23, janek wrote:
anyway, this patch LTGM.
Thanks, Janek!
The patch has passed countdown, but in view of the fact that a stable
release is on the horizon, it may not be appropriate to push it at this
time.
On the other hand, an argument for pushing it right away might be to
On 2013/04/23 19:03:18, david.nalesnik wrote:
On 2013/04/23 13:14:23, janek wrote:
> anyway, this patch LTGM.
Thanks, Janek!
The patch has passed countdown, but in view of the fact that a stable
release is
on the horizon, it may not be appropriate to push it at this time.
On the other
On 2013/04/23 19:38:09, dak wrote:
On 2013/04/23 19:03:18, david.nalesnik wrote:
> On 2013/04/23 13:14:23, janek wrote:
> > anyway, this patch LTGM.
>
> Thanks, Janek!
>
> The patch has passed countdown, but in view of the fact that a
stable release
is
> on the horizon, it may not be appropriat
Sorry for the late review.
https://codereview.appspot.com/8647044/diff/5001/input/regression/offsets.ly
File input/regression/offsets.ly (right):
https://codereview.appspot.com/8647044/diff/5001/input/regression/offsets.ly#newcode5
input/regression/offsets.ly:5: the @code{\\offset} command. Th
Confirming that the .pdf size doubles, but only if we measure relative
to the size of the smaller .pdfs we get if we know to use
-dno-point-and-click. The time required to process the larger .ps was
less that 1% the total time to compile my test .ly files.
Confirming that the resulting larger .p
https://codereview.appspot.com/8647044/diff/5001/scm/music-functions.scm
File scm/music-functions.scm (right):
https://codereview.appspot.com/8647044/diff/5001/scm/music-functions.scm#newcode2103
scm/music-functions.scm:2103: ; head of the alist. We reverse the alist
so our search will return
O
lgtm
Somewhere I'll have to write down the definition
"cross-staff": true for a grob whose placement or size could depend on
the spacing of staves on the page.
https://codereview.appspot.com/8557044/diff/6001/lily/side-position-interface.cc
File lily/side-position-interface.cc (right):
https:/
On 2013/04/23 21:56:07, Keith wrote:
Confirming that the .pdf size doubles, but only if we measure relative
to the
size of the smaller .pdfs we get if we know to use
-dno-point-and-click. The
time required to process the larger .ps was less that 1% the total
time to
compile my test .ly fil
On 24 avr. 2013, at 01:06, k-ohara5...@oco.net wrote:
> lgtm
>
> Somewhere I'll have to write down the definition
> "cross-staff": true for a grob whose placement or size could depend on
> the spacing of staves on the page.
It's not quite that. In the definition above, a treble clef on the 5th
Phil Holmes-2 wrote
> - Original Message -
> From: "David Kastrup" <
> dak@
> >
> To: <
> lilypond-devel@
> >
> Sent: Tuesday, April 23, 2013 1:08 PM
> Subject: Re: Point and Click does not work on Windows
>
>
>> ArnoldTheresius <
> Arnold.Wendl@
> > writes:
>>> Who will (and can o
36 matches
Mail list logo
