On Sat, Jan 25, 2020 at 1:47 PM Han-Wen Nienhuys wrote:
> 7.2 seconds end-to-end includes 1.7s of GC, and 2.0s of reading/compiling SCM.
>
> On guile 1.8, with GS disabled, the end to end runtime is
>
> 3.568s including 0.33s for GC and 0.32s for reading the SCM.
>
> These timings are internally c
Am So., 26. Jan. 2020 um 14:41 Uhr schrieb Han-Wen Nienhuys :
>
> See https://github.com/hanwen/lilypond/pull/1
>
> This has a stack of dependent commits (see below). I don't know how to
> deal with this on Rietveld.
>
> commit 3c8081d25b53529efe687ffe9e92ef48f5d11ea2
> Author: Han-Wen Nienhuys
>
See https://github.com/hanwen/lilypond/pull/1
This has a stack of dependent commits (see below). I don't know how to
deal with this on Rietveld.
commit 3c8081d25b53529efe687ffe9e92ef48f5d11ea2
Author: Han-Wen Nienhuys
Date: Sun Jan 26 12:19:56 2020 +0100
Parse inline scheme using Overlay_
pkx1...@posteo.net writes:
> On 25/01/2020 14:26, David Kastrup wrote:
>> ...
>> 16.04 is all very nice, but relying on non-updated legacy systems for
>> proscribing the dependencies of a hot-of-the-presses release is not
>> providing much of value.
>
> Talking of which ... should I (we) remove th
Han-Wen Nienhuys writes:
> On Sat, Jan 25, 2020 at 8:16 PM David Kastrup wrote:
>> > $ gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
>> > -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
>> > -dAutoRotatePages=/None -dPrinted=false -sOutputFile=mozart-hr
On Sat, Jan 25, 2020 at 8:16 PM David Kastrup wrote:
> > I still get
> >
> > input/regression/mozart-hrn-3.ly:31:9: error: not a markup
> >
> > #(string-append "It has been typeset and placed in the public "
>
> Frankly, that one looks like a nightmare that should not happen. Does
> it s
On 25/01/2020 14:26, David Kastrup wrote:
...
16.04 is all very nice, but relying on non-updated legacy systems for
proscribing the dependencies of a hot-of-the-presses release is not
providing much of value.
Talking of which ... should I (we) remove the instructions about
specific Distributio
On Sat, Jan 25, 2020 at 8:16 PM David Kastrup wrote:
> > $ gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
> > -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
> > -dAutoRotatePages=/None -dPrinted=false -sOutputFile=mozart-hrn-3.pdf
> > -c.setpdfwrite -f/tm
Han-Wen Nienhuys writes:
> On Sat, Jan 25, 2020 at 3:50 PM David Kastrup wrote:
>> > That patch is papering over a problem rather than fixing it. It might
>> > be a reoccurence of something like
>> >
>> > commit c01a2a757e3c59727bdfa8d77568bf42525fbe05
>> > Author: Andy Wingo
>> > Date: Thu
On Sat, Jan 25, 2020 at 3:50 PM David Kastrup wrote:
> > That patch is papering over a problem rather than fixing it. It might
> > be a reoccurence of something like
> >
> > commit c01a2a757e3c59727bdfa8d77568bf42525fbe05
> > Author: Andy Wingo
> > Date: Thu Jun 23 11:47:42 2016 +0200
> >
> >
David Kastrup writes:
> Han-Wen Nienhuys writes:
>
>> With https://codereview.appspot.com/551390047/
>
> That patch is papering over a problem rather than fixing it. It might
> be a reoccurence of something like
>
> commit c01a2a757e3c59727bdfa8d77568bf42525fbe05
> Author: Andy Wingo
> Date:
Jonas Hahnfeld writes:
> Am Samstag, den 25.01.2020, 15:26 +0100 schrieb David Kastrup:
>> Jonas Hahnfeld via Discussions on LilyPond development
>> <
>> lilypond-devel@gnu.org
>> > writes:
>>
>> > Am Samstag, den 25.01.2020, 14:45 +0100 schrieb Thomas Morley:
>> > > Am Sa., 25. Jan. 2020 um 13:
Am Samstag, den 25.01.2020, 15:26 +0100 schrieb David Kastrup:
> Jonas Hahnfeld via Discussions on LilyPond development
> <
> lilypond-devel@gnu.org
> > writes:
>
> > Am Samstag, den 25.01.2020, 14:45 +0100 schrieb Thomas Morley:
> > > Am Sa., 25. Jan. 2020 um 13:48 Uhr schrieb Han-Wen Nienhuys <
Jonas Hahnfeld via Discussions on LilyPond development
writes:
> Am Samstag, den 25.01.2020, 14:45 +0100 schrieb Thomas Morley:
>> Am Sa., 25. Jan. 2020 um 13:48 Uhr schrieb Han-Wen Nienhuys <
>> hanw...@gmail.com
>> >:
>> > [...]
>> > I think it is clear that we should not be targeting GUILE 2.0
Am Samstag, den 25.01.2020, 14:45 +0100 schrieb Thomas Morley:
> Am Sa., 25. Jan. 2020 um 13:48 Uhr schrieb Han-Wen Nienhuys <
> hanw...@gmail.com
> >:
> > [...]
> > I think it is clear that we should not be targeting GUILE 2.0, but GUILE
> > 2.2.
>
> I dropped any work for guile-2.0 long ago.
>
Am Sa., 25. Jan. 2020 um 15:03 Uhr schrieb Han-Wen Nienhuys :
>
> On Sat, Jan 25, 2020 at 2:45 PM Thomas Morley
> wrote:
> > Compiling the same file with my slow loptop and
> > released 2.19.83
> >
> ..
> > Without the error with string-append
>
> interesting. I was on 2.2.4; maybe these were bug
On Sat, Jan 25, 2020 at 2:45 PM Thomas Morley wrote:
> Compiling the same file with my slow loptop and
> released 2.19.83
>
..
> Without the error with string-append
interesting. I was on 2.2.4; maybe these were bugs fixed in 2.2.6 or
beyond. Let me see if I can upgrade things.
> > These timings
Han-Wen Nienhuys writes:
> With https://codereview.appspot.com/551390047/
That patch is papering over a problem rather than fixing it. It might
be a reoccurence of something like
commit c01a2a757e3c59727bdfa8d77568bf42525fbe05
Author: Andy Wingo
Date: Thu Jun 23 11:47:42 2016 +0200
Fix
Am Sa., 25. Jan. 2020 um 13:48 Uhr schrieb Han-Wen Nienhuys :
>
> With https://codereview.appspot.com/551390047/
> it looks like I can run LilyPond against GUILE 2.2 mostly:
>
>
> $ time lilypond input/regression/mozart-hrn-3.ly
> GNU LilyPond 2.21.0
> Import (ice-9 threads) to have access to `call
With https://codereview.appspot.com/551390047/
it looks like I can run LilyPond against GUILE 2.2 mostly:
$ time lilypond input/regression/mozart-hrn-3.ly
GNU LilyPond 2.21.0
Import (ice-9 threads) to have access to `call-with-new-thread'.
Import (ice-9 threads) to have access to `current-thread'
20 matches
Mail list logo